# CVE-2012-10036: Project Pier <= 0.8.8 Arbitrary File Upload RCE

> Unauthenticated attackers can upload malicious PHP files to Project Pier, leading to remote code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-hxc7-vv4w-87m3

## What is CVE-2012-10036?

CVE-2012-10036 is a critical vulnerability in ProjectPier, published on 8 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Project Pier 0.8.8 and earlier contains an unauthenticated arbitrary file upload vulnerability in tools/upload_file.php. The upload handler fails to validate the file type or enforce authentication, allowing remote attackers to upload malicious PHP files directly into a web-accessible directory. The uploaded file is stored with a predictable suffix and can be executed by requesting its URL, resulting in remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2012-10036?


## How do I fix CVE-2012-10036?

No fix has been published for CVE-2012-10036 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-10036 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-10036 exists.

Public exploit code:

- Project Pier Arbitrary File Upload Vulnerability (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-10036 and fix it if it is affected.

What it is: CVE-2012-10036 is a critical vulnerability in ProjectPier, published on 8 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-10036 exists.

Affected product: ProjectPier. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-10036/ (Markdown: https://insights.sbomify.com/CVE-2012-10036/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-10036
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-10036
- OSV: https://osv.dev/vulnerability/CVE-2012-10036

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-10036/
Summaries are generated and may contain mistakes; the official description above is the record.