Loading vulnerability…
CVE-2026-58048 is a critical privilege-escalation vulnerability in cPanel & WHM and WP Squared affecting the database management workflow used when renaming databases. The flaw stems from improper preservation of SQL mode during the rename process. In that workflow, the platform creates a replacement database, migrates data, recreates grants and stored code, and removes the original database and permissions. Because SQL mode is not preserved correctly, an authenticated cPanel user with access to the MySQL or MariaDB feature can cause SQL statements to execute in the database root context rather than the user’s intended restricted context. The issue is classified as CWE-89 and enables arbitrary database-command execution with administrative database privileges.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains two Python tools centered on alleged CVE-2026-58048 in cPanel & WHM: `exploit.py` (full exploit toolkit) and `safecheck.py` (non-intrusive checker). The exploit script is a standalone Python CLI utility, not tied to a common exploitation framework. It uses `requests`, optional proxying, configurable SSL verification, logging, threading for multi-target operation, and interactive credential prompting. Based on the README and visible code, its workflow is to normalize and parse a target URL, communicate with cPanel over HTTPS, authenticate with supplied cPanel credentials, query version information, and then abuse the cPanel UAPI database rename path (`/execute/Mysql/rename_database`) to inject attacker-controlled SQL under MySQL root context. Claimed post-exploitation features include arbitrary SQL execution, reverse shell via UDF, file read, MySQL password changes, cPanel user creation, verification, and mass scanning. `safecheck.py` is a separate Python CLI intended for defensive assessment. It performs target normalization, HTTP requests to the cPanel service, version/risk checks, optional JSON/log output, and avoids the intrusive exploit path. It is best classified as a detection/assessment companion rather than the main exploit. Repository structure is minimal: 6 files total, with 2 code files (`exploit.py`, `safecheck.py`), a README describing usage and endpoints, a requirements file (`requests`, `urllib3`, `colorama`, `pymysql`), and standard metadata files. Overall, this is an operational exploit toolkit with a companion scanner/checker, targeting authenticated web-based access to cPanel services and subsequent database-level privilege abuse.
Repository contains a standalone Python exploit PoC and a companion Docker-based simulation lab for CVE-2026-58048. The main exploit file is poc.py, which automates interaction with cPanel UAPI endpoints to create a database, manipulate SQL mode, and trigger a vulnerable database rename operation that executes attacker-supplied SQL as MySQL root. The exploit supports authenticated real-target use with username/password or API token, and also auto-detects a local lab mode with custom helper endpoints. Primary capability is privilege escalation from authenticated cPanel user to arbitrary MySQL root SQL execution. Built-in payload presets go beyond simple verification: they can create an administrative MySQL account, write a PHP webshell into a web root using INTO OUTFILE, read files with LOAD_FILE, dump MySQL user data, and attempt UDF-based OS command execution. This makes the repository more than a minimal PoC; it is an operational exploit with multiple post-exploitation SQL payload options. Repository structure is simple: README.md documents the vulnerability, affected versions, usage, and payload presets; poc.py is the exploit entry point; simulate.py generates and manages a Docker lab including MariaDB, a Flask-based vulnerable API simulator, and an Apache/PHP container for demonstrating file-write-to-webshell chaining. requirements.txt lists Python dependencies. The lab exposes ports 13306, 18080, and 18081 and implements endpoints such as /api/set_sql_mode and /api/rename_database to emulate the vulnerable behavior. Overall purpose: demonstrate and weaponize a SQL injection flaw in cPanel database rename handling where attacker-controlled ANSI_QUOTES session state is preserved into a privileged root-context rename operation, enabling breakout from identifier quoting and execution of arbitrary SQL.
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.
58 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A database privilege escalation vulnerability affecting cPanel.
A critical cPanel privilege escalation vulnerability that allows an authenticated cPanel account holder with MySQL/MariaDB access to execute arbitrary database commands with full administrative privileges, with possible operating-system-level compromise depending on configuration.
A critical privilege-escalation vulnerability in cPanel & WHM that allows an authenticated cPanel user with MySQL or MariaDB access to execute arbitrary SQL commands with full database administrative privileges, potentially leading to root-level server compromise in some configurations.
A database privilege escalation vulnerability in WebPros cPanel caused by improper preservation of SQL mode during database renaming, allowing execution of SQL in root context.
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.