CVE-2005-2612: Code Injection
First published: Wed Aug 17 2005(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | =1.0 | |
| WordPress | =1.0.1 | |
| WordPress | =1.0.2 | |
| WordPress | =1.2 | |
| WordPress | =1.5 | |
| WordPress | =1.5.1 | |
| WordPress | =1.5.1.2 | |
| WordPress | =1.5.1.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2005-2612?
CVE-2005-2612 is considered a critical vulnerability due to the potential for remote code execution.
How do I fix CVE-2005-2612?
To fix CVE-2005-2612, upgrade to the latest version of WordPress that is not affected by this vulnerability.
Which versions of WordPress are affected by CVE-2005-2612?
CVE-2005-2612 affects WordPress versions 1.5.1.3 and earlier.
Can CVE-2005-2612 be exploited remotely?
Yes, CVE-2005-2612 can be exploited remotely by attackers using specially crafted cookies.
What type of vulnerability is CVE-2005-2612?
CVE-2005-2612 is a direct code injection vulnerability.
- agent/references
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/weakness
- agent/author
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/wordpress
- canonical/wordpress
- version/wordpress/1.0
- version/wordpress/1.0.1
- version/wordpress/1.0.2
- version/wordpress/1.2
- version/wordpress/1.5
- version/wordpress/1.5.1
- version/wordpress/1.5.1.2
- version/wordpress/1.5.1.3