Vulnerabilities · 2006 · Wordpress
CVE-2006-2667
Wordpress vulnerability
Direct static code injection vulnerability in WordPress 2.0.2 and earlier allows remote attackers to execute arbitrary commands by inserting a carriage return and PHP code when updating a profile, which is appended after a special comment sequence into files in (1) wp-content/cache/userlogins/ (2) wp-content/cache/users/ which are later included by cache.php, as demonstrated using the displayname argument.
Affected products
Wordpress. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Wordpress runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- secunia.com/advisories/20271 · Patch
- retrogod.altervista.org/wordpress_202_xpl.html · Exploit
- secunia.com/advisories/20608
- www.gentoo.org/security/en/glsa/glsa-200606-08.xml
- www.osvdb.org/25777
- www.securityfocus.com/archive/1/435039/100/0/threaded
- www.securityfocus.com/bid/18372
- www.vupen.com/english/advisories/2006/1992
- nvd.nist.gov/vuln/detail/CVE-2006-2667
- cve.org/CVERecord?id=CVE-2006-2667
More vulnerabilities in Wordpress products
CVE-2024-31211CVE-2024-31210CVE-2024-8914CVE-2024-4439CVE-2023-39999CVE-2023-38000CVE-2023-22622CVE-2023-5561All 407
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.