Loading vulnerability…
A direct code injection vulnerability exists in WordPress 1.5.1.3 and earlier, where the application fails to properly sanitize input from the cache_lastpostdate[server] cookie. This allows remote attackers to inject and execute arbitrary PHP code on the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (wp_lastpost_exec.rb) that exploits an arbitrary PHP code execution vulnerability in WordPress versions prior to 1.5.1.3 (CVE-2005-2612). The exploit targets servers with the 'register_globals' PHP option enabled, a common configuration in older hosting environments. The module works by sending a specially crafted HTTP request with a malicious cookie to the WordPress site, triggering the vulnerability and executing attacker-supplied PHP code. The payload is delivered using Metasploit's payload system and is encoded for delivery. The only configurable endpoint is the URI path to the WordPress installation, which defaults to '/'. The exploit is operational and allows for arbitrary code execution on the target server. The repository is structured as a single Ruby file compatible with the Metasploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.