Loading vulnerability…
A remote PHP code execution vulnerability exists in the WordPress W3 Total Cache Plugin version 0.9.2.8. The vulnerability allows an attacker to execute arbitrary PHP code on the server by exploiting improper input validation or insecure handling of user-supplied data within the plugin.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (wp_total_cache_exec.rb) that exploits a PHP code injection vulnerability in the WordPress W3 Total Cache plugin (versions <= 0.9.2.8) and WP Super Cache (<= 1.2). The exploit works by posting a specially crafted comment containing a PHP payload using the 'mfunc' macro, which is then executed by the vulnerable plugin. The module can operate with or without authentication, depending on the target's comment settings, and will attempt to find a valid post ID for comment injection. Upon successful exploitation, arbitrary PHP code (the attacker's payload) is executed on the server. The module is operational and provides remote code execution capabilities. The only endpoint is the target WordPress site, which is accessed via HTTP requests to post comments and trigger the payload. The code is written in Ruby and is structured as a standard Metasploit exploit module.
This repository provides a Python exploit script (w3tc_rce_exploit.py) targeting CVE-2013-2010, a remote code execution vulnerability in the W3 Total Cache plugin for WordPress. The exploit works by sending a crafted comment containing arbitrary PHP code to the vulnerable endpoint '/wp-comments-post.php' on the target site. The script takes two arguments: the target URL and the PHP payload to execute. If successful, the payload is executed on the server, granting the attacker remote code execution capabilities. The repository consists of a single file (README.md) that contains both usage instructions and the full exploit code. The exploit is operational, allowing attackers to specify custom PHP payloads for execution.
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.