Public exploit available
Public proof-of-concept or exploit code exists (ExploitDB / Metasploit / Nuclei).

CVE-2006-2667 — Static Code Injection in Wordpress

5 documents5 sources
Severity
7.5HIGHNVD
EPSS
32.2%
top 3.15%
CISA KEV
Not in KEV
Exploit
PoC available
Public exploit / PoC exists
Affected products
2
WordpressDebian Wordpress
Timeline
PublishedMay 30
Latest updateMay 1

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.

CVSS vector

AV:N/AC:L/C:P/I:P/A:PExploitability: 10.0 | Impact: 6.4

Affected Packages3 packages

▶debiandebian/wordpress< wordpress 2.0.3-1 (bookworm)
▶Debianwordpress/wordpress< 2.0.3-1+3

Patches

Patch: secunia.com ↗Patch: secunia.com ↗

🔴Vulnerability Details

2
GHSA
GHSA-77v7-f4fr-3hjf: Direct static code injection vulnerability in WordPress 2↗2022-05-01
▶
OSV
CVE-2006-2667: Direct static code injection vulnerability in WordPress 2↗2006-05-30
▶

💥Exploits & PoCs

1
Exploit-DB
WordPress Core 2.0.2 - 'cache' Remote Shell Injection↗2006-05-25
▶

📋Vendor Advisories

1
Debian
CVE-2006-2667: wordpress - Direct static code injection vulnerability in WordPress 2.0.2 and earlier allows...↗2006
▶
CVE-2006-2667 — Static Code Injection in Wordpress | cvebase