Loading vulnerability…
CVE-2011-4899 affects the WordPress installation component in WordPress 3.3.1 and earlier. The vulnerability is in wp-admin/setup-config.php, which does not adequately validate that the supplied MySQL service is an appropriate backend for the installation process. An unauthenticated remote attacker can supply attacker-controlled values for database connection parameters such as the database host and database name, causing the application to interact with an arbitrary database under the attacker’s control. By steering the installation workflow to malicious database content, an attacker can subsequently trigger static code injection and cross-site scripting conditions. Reported exploitation paths include delivery through crafted HTTP requests and through malicious MySQL query results returned from the attacker-controlled database. In realistic deployments, this can be chained into PHP code execution through normal WordPress administrative functionality after the malicious installation state is established.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
1 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.