CVE-2012-10036 affects Project Pier 0.8.8 and earlier. The application contains an arbitrary file upload vulnerability in tools/upload_file.php where the upload handler does not enforce authentication and does not properly validate uploaded file types. As a result, a remote attacker can submit a malicious PHP file and have it written into a web-accessible directory. Because the uploaded file is stored with a predictable suffix and remains reachable over HTTP, the attacker can subsequently request the uploaded file directly and cause the server to execute attacker-controlled PHP code. The issue is therefore an unauthenticated file upload flaw that leads to remote 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 contains a single Metasploit module (projectpier_upload_exec.rb) that exploits an arbitrary file upload vulnerability in Project Pier (CVE-2012-10036). The exploit targets Project Pier versions 0.8.0 through 0.8.8 running on Apache web servers. The module leverages an unauthenticated file upload endpoint (/tools/upload_file.php) to upload a PHP payload, which is then executed by making an HTTP request to the uploaded file. The exploit supports both PHP and Linux x86 payloads, allowing for remote code execution with the privileges of the web server. The module includes a check method to verify the target's vulnerability and is fully integrated into the Metasploit framework, making it weaponized and easily customizable. The only file in the repository is the Metasploit module itself, written in Ruby.
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.
7 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.