Loading vulnerability…
PHPMemcachedAdmin versions 1.2.2 and earlier are vulnerable to remote code execution due to improper handling of serialized data and filename concatenation. An attacker can manipulate serialized data and the filename such that a malicious PHP file is created in the webroot, which can then be executed remotely, allowing arbitrary PHP code execution.
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 is a proof-of-concept exploit for CVE-2014-8731, targeting PHPMemcachedAdmin version 1.2.2 and earlier. It contains two files: a README.md with usage instructions and background, and attack.py, a Python script that automates the exploitation process. The exploit works by abusing the way PHPMemcachedAdmin handles serialized data and file creation, allowing an attacker to upload a PHP webshell to the server's webroot. The script first sends a crafted POST request to /configure.php to add a malicious cluster configuration, then triggers the writing of the webshell via /stats.php. Once the webshell is in place, the script accesses it and passes a user-supplied command via the 'cmd' GET parameter, displaying the output. The main attack vector is network-based, requiring HTTP access to the vulnerable application. The endpoints involved are /configure.php, /stats.php, and the resulting webshell URL. The exploit is a functional proof-of-concept and does not include advanced features or payload customization beyond the basic webshell.
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.