Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2012-10036: Unauthenticated Arbitrary File Upload RCE in Project Pier tools/upload_file.php

Published Aug 8, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS2.0%81st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Projectpier
IdentifiersCVE-2012-10036CWE-434 · Unrestricted Upload of File with…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated remote attacker to achieve remote code execution in the security context of the web server or PHP runtime. This can enable full compromise of the Project Pier instance, including reading or modifying application data, deploying persistent web shells, pivoting further into the environment, and potentially escalating privileges depending on host configuration and file permissions.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, block external access to tools/upload_file.php or remove the file if it is not required. Restrict access to the application behind authentication or network controls, disable execution of PHP and other server-side scripts in upload directories, and move upload storage to a non-web-accessible location. Web application firewall rules may help detect or block suspicious multipart upload requests, but should not be relied upon as the sole control. Conduct incident response review for existing web shells or unauthorized uploads.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version if one is available from the vendor or maintainers. If no patched release is available, modify tools/upload_file.php to require authentication and authorization before processing uploads, strictly validate allowed file types using a server-side allowlist, reject executable script extensions such as .php, .phtml, and similar variants, and store uploaded files outside the web root so they cannot be executed directly. Additionally, configure the web server to disable script execution in upload directories and review the application for any previously uploaded malicious files.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ProjectpierProjectpierapplication
FAQ

Frequently asked questions

Is CVE-2012-10036 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2012-10036 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2012-10036?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2012-10036, the earliest disclosed Oct 8, 2012.
Is there a patch for CVE-2012-10036?
Upgrade to a fixed version if one is available from the vendor or maintainers. If no patched release is available, modify tools/upload_file.php to require authentication and authorization before processing uploads, strictly validate allowed file types using a server-side allowlist, reject executable script extensions such as .php, .phtml, and similar variants, and store uploaded files outside the web root so they cannot be executed directly.
What products are affected by CVE-2012-10036?
Projectpier.
How severe is CVE-2012-10036?
CVE-2012-10036 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 2.0% (81st percentile) as of Oct 16, 2026.
Activity feed

Recent activity

7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.