How severe is CVE-2005-2612?

CVE-2005-2612 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-2612 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 39% (98th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-2612?

CVE-2005-2612 primarily affects Wordpress. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-2612?

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-2005-2612 published?

CVE-2005-2612 was published on 2005-08-17 and last updated on 2026-06-16.

CVE-2005-2612

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

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 39% (98th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Wordpress
Published: 2005-08-17
Last modified: 2026-06-16

Description

Direct code injection vulnerability in WordPress 1.5.1.3 and earlier allows remote attackers to execute arbitrary PHP code via the cache_lastpostdate[server] cookie.

Frequently asked questions

What is CVE-2005-2612?: Direct code injection vulnerability in WordPress 1.5.1.3 and earlier allows remote attackers to execute arbitrary PHP code via the cache_lastpostdate[server] cookie.
How severe is CVE-2005-2612?: CVE-2005-2612 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-2612 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 39% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2612?: CVE-2005-2612 primarily affects Wordpress. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-2612?: 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-2005-2612 published?: CVE-2005-2612 was published on 2005-08-17 and last updated on 2026-06-16.

References

Affected products (8)

cpe:2.3:a:wordpress:wordpress:1.0:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.0.1:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.0.2:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.2:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.5:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.5.1:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.5.1.2:*:*:*:*:*:*:*
cpe:2.3:a:wordpress:wordpress:1.5.1.3:*:*:*:*:*:*:*

More vulnerabilities in Wordpress

CVE-2012-2400 — Critical (CVSS 10.0): Unspecified vulnerability in wp-includes/js/swfobject.js in WordPress before 3.3.2 has unknown impact and attack…
CVE-2012-2399 — Critical (CVSS 10.0): Cross-site scripting (XSS) vulnerability in swfupload.swf in SWFupload 2.2.0.1 and earlier, as used in WordPress before…
CVE-2011-3125 — Critical (CVSS 10.0): Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors…
CVE-2011-3122 — Critical (CVSS 10.0): Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors…
CVE-2009-2853 — Critical (CVSS 10.0): Wordpress before 2.8.3 allows remote attackers to gain privileges via a direct request to (1) admin-footer.php, (2)…
CVE-2008-6767 — Critical (CVSS 10.0): wp-admin/upgrade.php in WordPress, probably 2.6.x, allows remote attackers to upgrade the application, and possibly…

All CVEs affecting Wordpress →