Loading vulnerability…
CVE-2009-1285 is a static code injection vulnerability in phpMyAdmin 3.x before 3.1.3.2. The flaw is in the getConfigFile function in setup/lib/ConfigFile.class.php, which allows attacker-controlled input to be written into generated configuration files as arbitrary PHP code. Because phpMyAdmin configuration files are PHP, improper neutralization of input during configuration file generation can result in injected code being stored in the config and later executed by the PHP interpreter.
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 single Metasploit module (modules/exploits/unix/webapp/phpmyadmin_config.rb) that exploits a code injection vulnerability in phpMyAdmin's setup script (CVE-2009-1151). The exploit targets phpMyAdmin versions 2.11.x < 2.11.9.5 and 3.x < 3.1.3.1, allowing an attacker to inject arbitrary PHP code into the configuration file (config/config.inc.php) by abusing the setup script (scripts/setup.php). The module first retrieves a CSRF token and session cookie from the setup script, then crafts a malicious configuration payload containing the attacker's PHP code, and submits it via a POST request. Finally, it triggers execution of the payload by requesting the modified config file. The exploit is fully weaponized, supporting arbitrary PHP payloads via the Metasploit framework. The main attack vector is network-based, requiring HTTP access to the vulnerable phpMyAdmin instance. The repository is structured as a single Ruby file compatible with Metasploit, and all relevant logic is contained within this file.
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.
2 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.