CVE-2005-2612

NONECVSS 0.0Weaponized

0.0

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.

CVSS v3: —
EG Score: —
EPSS: 98.8%
KEV: Not listed

Published

August 17, 2005

Last Modified

April 16, 2026

References (4)

cve@mitrehttp://archives.neohapsis.com/archives/fulldisclosure/2005-08/0234.html
cve@mitrehttp://secunia.com/advisories/16386
af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/fulldisclosure/2005-08/0234.html
af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/16386

Data Freshness Timeline

(refreshed 5× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-29 13:40 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-23 11:34 UTCOSV refresh
2026-05-21 22:38 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

Exploit-DBEDB-16895✓ verified
First seen Jul 3, 2010
WordPress Core 1.5.1.3 - 'cache_lastpostdate' Arbitrary Code Execution (Metasploit)
Open source ↗
Metasploitexploit/unix/webapp/wp_lastpost_exec✓ verified
First seen Aug 9, 2005
WordPress cache_lastpostdate Arbitrary Code Execution
Open source ↗

Frequently asked(4)

What is CVE-2005-2612?

CVE-2005-2612 is a none vulnerability published on August 17, 2005. 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.

When was CVE-2005-2612 disclosed?

CVE-2005-2612 was first published in the National Vulnerability Database on August 17, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2005-2612 actively exploited?

CVE-2005-2612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2005-2612?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2612, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2005-2612

Explore →

Is Your Infrastructure Affected by CVE-2005-2612?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2005-2612

📅 Published

🔄 Last Modified

🔗 References (4)