W3 Total Cache plugin for WordPress versions up to and including 2.7.5 exposes Google OAuth API secrets in plaintext within the publicly accessible plugin source code. This allows unauthenticated attackers to obtain these secrets and potentially impersonate the plugin in interactions with Google services.
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 (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2023-5359, a cleartext storage vulnerability in the W3 Total Cache WordPress plugin (versions <= 2.7.5). The vulnerability allows remote attackers to access sensitive credentials stored in unprotected PHP files within the plugin directory, which are accessible via HTTP if not properly restricted. The repository consists of two files: a detailed README.md explaining the vulnerability, affected files, exploitation methods, and mitigation steps; and poc.py, a Python script that automates detection and exploitation. The script checks for the presence of W3 Total Cache on a target site, then attempts to access a set of known vulnerable PHP files, extracting credentials using regular expressions. The main attack vector is network-based, requiring only HTTP access to the target. The exploit is operational, providing real credential extraction if the target is vulnerable. No fake or destructive actions are present; the script is focused on information disclosure. The endpoints targeted are specific plugin PHP files under /wp-content/plugins/w3-total-cache/.
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.