Loading vulnerability…
CVE-2012-10049 affects WebPageTest 2.6 and earlier. The vulnerability is an arbitrary file upload flaw in the resultimage.php script, which does not properly validate or sanitize user-supplied upload input before writing files to a publicly accessible directory. Because an attacker can upload a PHP file to a web-accessible location, the flaw can be leveraged to execute arbitrary PHP code on the server. Successful exploitation results in remote code execution in the security context of the web server process.
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 (webpagetest_upload_exec.rb) that exploits a file upload vulnerability in WebPageTest v2.6 or older (CVE-2012-10049). The exploit abuses the resultimage.php endpoint, which fails to properly validate uploaded files, allowing an attacker to upload a malicious PHP file to the web-accessible /results/ directory. The module first checks for the presence of WebPageTest by requesting /index.php and /work/resultimage.php. If the target is vulnerable, it uploads a PHP payload via a POST request to /work/resultimage.php, then triggers execution by requesting the uploaded file in /results/. The exploit provides remote code execution as the web server user. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.
5 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.