CVE-2025-12539 affects the TNC Toolbox: Web Performance plugin for WordPress in all versions up to and including 1.4.2. The vulnerability is caused by the plugin's "Tnc_Wp_Toolbox_Settings::save_settings" function storing cPanel API credentials—including hostname, username, and API key—in files under the web-accessible wp-content directory without adequate access protection. Because these files are reachable from the web, an unauthenticated attacker can retrieve the stored credentials. Exposure of valid cPanel API credentials can then be leveraged to interact directly with the cPanel API, enabling follow-on actions such as arbitrary file upload and remote code execution, potentially resulting in full compromise of the affected hosting environment.
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 exploit script (CVE-2025-12539.py) targeting the TNC Toolbox: Web Performance WordPress plugin (versions <= 1.4.2). The exploit leverages an unauthenticated sensitive information exposure vulnerability, where the plugin stores cPanel credentials in web-accessible files without proper access controls. The script first checks the plugin version by fetching the readme.txt file, then, if vulnerable, attempts to retrieve the cPanel username, API key, and server hostname from specific configuration files. The output is a structured JSON report containing the extracted credentials and vulnerability status. The repository also includes a README with detailed usage instructions, a requirements.txt specifying the 'requests' library, and a license file. The exploit is operational, providing real credential extraction if the target is vulnerable, and is not a mere detection script.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.