CVE-2006-2667
Last modified
CVE-2006-2667 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 14.27% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wordpress | Wordpress | <= 2.0.2 |
References
- http://secunia.com/advisories/20271Patch, Vendor Advisory
- http://secunia.com/advisories/20271Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2006-2667?
How severe is CVE-2006-2667?
How do I fix CVE-2006-2667?
Are you affected by CVE-2006-2667?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
