CVE-2025-12539

TNC Toolbox: Web Performance <= 1.4.2 - Unauthenticated Sensitive Information Exposure to Privilege Escalation/cPanel Account Takeover

2025-11-10 22:27
kr0d

Strategic Overview

Status
Patched in 2.0.0
Affected Version
<= 1.4.2
CVSS
10.0Critical
Weakness type
CWE-922 · Insecure Storage of Sensitive Information
CVE
CVE-2025-12539
View all TNC Toolbox: Web Performance vulnerabilities

At a glance

CVE-2025-12539 is a critical-severity Insecure Storage of Sensitive Information vulnerability in the TNC Toolbox WordPress plugin, affecting versions <= 1.4.2. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.0; sites on affected versions should update now. Disclosed November 2025, reported by kr0d.

Vulnerability Overview

The TNC Toolbox: Web Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.2. This is due to the plugin storing cPanel API credentials (hostname, username, and API key) in files within the web-accessible wp-content directory without adequate protection in the "Tnc_Wp_Toolbox_Settings::save_settings" function. This makes it possible for unauthenticated attackers to retrieve these credentials and use them to interact with the cPanel API, which can lead to arbitrary file uploads, remote code execution, and full compromise of the hosting environment.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-922: Insecure Storage of Sensitive Information

The product stores sensitive information without properly limiting read or write access by unauthorized actors.

Remediation

Update to version 2.0.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: TNC Toolbox 2.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C