# CVE-2012-10027: WordPress Plugin WP-Property <= 1.35.0 PHP File Upload

> Unauthenticated attackers can upload arbitrary PHP files via the uploadify script, leading to remote code execution on WordPress sites using the WP-Property plugin.

- **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:** 5 Aug 2025
- **Updated:** 26 May 2026
- **Also known as:** GHSA-jh5w-mx23-qhvp

## What is CVE-2012-10027?

CVE-2012-10027 is a critical vulnerability in WP-Property WordPress Plugin, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WP-Property plugin for WordPress up to and including version 1.35.0 contains an unauthenticated file upload vulnerability in the third-party `uploadify.php` script. A remote attacker can upload arbitrary PHP files to a temporary directory without authentication, leading to remote code execution.

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

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


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

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

## Is CVE-2012-10027 being exploited?

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

Public exploit code:

- WordPress WP-Property PHP File Upload Vulnerability (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-10027 is a critical vulnerability in WP-Property WordPress Plugin, published on 5 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-10027 exists.

Affected product: WP-Property WordPress Plugin. 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-10027/ (Markdown: https://insights.sbomify.com/CVE-2012-10027/index.md)
```

## Sources

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

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