CVE-2012-10027 affects the WP-Property plugin for WordPress through version 1.35.0. The vulnerability is an unauthenticated arbitrary file upload flaw in the bundled third-party uploadify.php script. Because the upload handler does not properly restrict or validate uploaded file types, a remote attacker can upload arbitrary PHP files to a temporary directory without authentication. If the uploaded file is reachable and executed by the web server's PHP interpreter, this results in remote code execution in the context of the WordPress/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.
uploadify.php script and, if necessary, deactivate the WP-Property plugin until a fixed version is deployed. Block direct web access to the vulnerable upload endpoint via web server rules or WAF controls. Configure the upload directory and temporary directories as non-executable, and prevent interpretation of PHP in user-writable paths. Monitor for unexpected PHP files in upload or temporary directories and review logs for suspicious requests to the upload handler.Patch, then assume compromise.
uploadify.php component. The vulnerable upload handler should enforce strict server-side validation of allowed file types, reject executable content such as PHP scripts, store uploads outside the web root or in a non-executable location, and ensure uploaded files cannot be directly executed. If no fixed version is available, remove the vulnerable script or the plugin entirely.1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module targeting a vulnerability in the WP-Property WordPress plugin (versions <= 1.35.0). The exploit abuses the 'uploadify.php' file, which allows unauthenticated file uploads to a temporary directory. The module uploads a PHP payload (customizable via Metasploit) and then executes it, resulting in arbitrary code execution on the target server. The main attack vector is network-based, targeting the web application's file upload functionality. The module includes detection (via a GET request to the vulnerable file) and exploitation (upload and execution of the payload). The only fingerprintable endpoint is the path to the vulnerable 'uploadify.php' file. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.