# CVE-2012-10064: Omni Secure Files < 0.1.14 Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files via the plupload example endpoint, potentially 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:** 16 Jan 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-x8vx-242v-r66p

## What is CVE-2012-10064?

CVE-2012-10064 is a critical vulnerability in Omnilogic Omni Secure Files, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Omni Secure Files plugin versions prior to 0.1.14 contain an arbitrary file upload vulnerability in the bundled plupload example endpoint. The /wp-content/plugins/omni-secure-files/plupload/examples/upload.php handler allows unauthenticated uploads without enforcing safe file type restrictions, enabling an attacker to place attacker-controlled files under the plugin's uploads directory. This can lead to remote code execution if a server-executable file type is uploaded and subsequently accessed.

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

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


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

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

## Is CVE-2012-10064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-10064 is a critical vulnerability in Omnilogic Omni Secure Files, published on 16 Jan 2026. 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-10064 exists.

Affected product: Omnilogic Omni Secure Files. 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-10064/ (Markdown: https://insights.sbomify.com/CVE-2012-10064/index.md)
```

## Sources

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

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