Loading vulnerability…
W3 Total Cache for WordPress through version 2.8.1 exposes its debug log file when debugging is enabled. An unauthenticated attacker can retrieve potentially sensitive information recorded in the publicly accessible log, including nonce values that may facilitate subsequent cross-site request forgery attacks.
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 Python proof-of-concept exploit for CVE-2024-12008, an information exposure vulnerability in the W3 Total Cache WordPress plugin. The main script (w3tc_log_exploit.py, referenced in the usage instructions) attempts to detect the presence of the W3 Total Cache plugin on a target site, then checks several common paths for exposed debug log files. If a log file is found, the script extracts nonce values and displays them, along with a sample of the log content. The script also suggests how these nonces could be used in CSRF attacks against the target's admin-ajax.php endpoint. The repository structure is minimal, consisting of a README and the main exploit script. The exploit is network-based, targeting publicly accessible WordPress sites with misconfigured W3 Total Cache plugin installations.
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.
4 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.