CVE-2006-2667

Public Exploit

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.

7.5
CVSS
Severity: High
CVSS 2.0 •
EPSS 27.40% Top 5%
Vendor Advisory gentoo.org Vendor Advisory secunia.com
Affected: n/a n/a
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2006-2667?
CVE-2006-2667 has been scored as a high severity vulnerability.
How to fix CVE-2006-2667?
To fix CVE-2006-2667, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2006-2667 being actively exploited in the wild?
It is possible that CVE-2006-2667 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~27% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.