Loading vulnerability…
CVE-2012-10026 affects the WordPress Asset-Manager plugin version 2.0 and below. The vulnerability is an unauthenticated arbitrary file upload flaw in upload.php, where the endpoint does not properly validate or restrict uploaded file types. As a result, a remote attacker can upload a malicious PHP script to a predictable temporary directory and then invoke that uploaded file directly over HTTP. Successful exploitation leads to remote code execution in the 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 targeting a vulnerability (CVE-2012-10026) in the WordPress Asset-Manager plugin (versions 2.0 and below). The exploit abuses the 'upload.php' endpoint in the plugin, which allows unauthenticated file uploads to a temporary directory. The module uploads a PHP payload and then triggers its execution by sending a GET request to the uploaded file. The exploit provides remote code execution as the web server user. The code is written in Ruby and follows the standard Metasploit module structure, including detection and exploitation routines. The main fingerprintable endpoints are the vulnerable upload endpoint and the location where the payload is executed. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads.
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.
4 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.