CVE-2006-2667: Code Injection
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 Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2006-2667?
The severity of CVE-2006-2667 is considered to be critical, as it allows remote attackers to execute arbitrary PHP commands.
How do I fix CVE-2006-2667?
To fix CVE-2006-2667, update your WordPress installation to version 2.0.3 or later, as these versions contain the necessary security patches.
Which versions of WordPress are affected by CVE-2006-2667?
CVE-2006-2667 affects WordPress versions 2.0.2 and earlier.
Can CVE-2006-2667 lead to full system compromise?
Yes, CVE-2006-2667 can potentially lead to full system compromise by allowing arbitrary command execution on the server.
What types of attacks can be performed through CVE-2006-2667?
Attacks through CVE-2006-2667 could involve remote code execution, allowing attackers to manipulate or control server operations.