Loading vulnerability…
A trojanized version of phpMyAdmin 3.5.2.2 was distributed via the SourceForge mirror cdnetworks-kr-1 in 2012. The compromised archive (phpMyAdmin-3.5.2.2-all-languages.zip) contained a maliciously modified server_sync.php file, which introduced a backdoor allowing remote attackers to execute arbitrary PHP code through an eval injection. The js/cross_framing_protection.js file was also altered. This was not a vulnerability in the phpMyAdmin codebase itself, but rather a supply chain compromise of the distribution channel.
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 that exploits a backdoor in phpMyAdmin version 3.5.2.2, specifically targeting installations compromised via a malicious SourceForge mirror. The exploit works by sending a POST request to the /phpMyAdmin/server_sync.php endpoint, which was backdoored to allow arbitrary PHP code execution via the 'c' POST parameter. The module allows the attacker to send a Metasploit payload (arbitrary PHP code) to the vulnerable endpoint, resulting in remote code execution on the target server. The module is written in Ruby and leverages Metasploit's HTTP client mixin. The only fingerprintable endpoint is the server_sync.php file within the phpMyAdmin directory. The exploit is operational and requires the target to be running the specific compromised version of phpMyAdmin.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.