Loading vulnerability…
WordPress W3 Total Cache versions before 0.9.4 improperly process the SubscribeURL value supplied in SubscriptionConfirmation JSON data. An unauthenticated remote attacker can provide a local-file URI or otherwise attacker-controlled resource reference, causing the application to retrieve and disclose arbitrary files accessible to the web-server process.
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 provides a Python-based exploit and scanner for two vulnerabilities in the W3 Total Cache WordPress plugin: CVE-2019-6715 (Arbitrary File Read) and CVE-2024-12365 (SSRF/Info Disclosure). The main logic is contained in a script (shown in README.md) that checks the target for the W3 Total Cache plugin, determines its version, and attempts to exploit the vulnerable endpoint '/wp-content/plugins/w3-total-cache/pub/sns.php' by sending a crafted JSON payload. If successful, the exploit can read arbitrary files from the server (default: /etc/passwd) and confirm the presence of the vulnerabilities. The repository consists of a single file containing both usage instructions and the full exploit code, written in Python. The attack vector is network-based, requiring access to the target's web interface. The exploit is operational, providing real file read capability and version detection.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.