CVE-2006-2667

CVE-2006-2667 is a high-severity vulnerability in Wordpress with a CVSS 2.0 base score of 7.5. Its EPSS exploit-prediction score of 15% places it in the 96th percentile, indicating an elevated likelihood of exploitation.

Key facts

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.

Frequently asked questions

What is CVE-2006-2667?
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.
How severe is CVE-2006-2667?
CVE-2006-2667 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-2667 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 15% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-2667?
CVE-2006-2667 affects Wordpress. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2006-2667?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2006-2667 published?
CVE-2006-2667 was published on 2006-05-30 and last updated on 2026-06-16.

References

Affected products (1)

More vulnerabilities in Wordpress

All CVEs affecting Wordpress →