# CVE-2012-1010: File upload in n/a

> Remote attackers can execute arbitrary PHP code by uploading a malicious ZIP file via the AllWebMenus plugin.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4m7w-g6rc-g3w7

## What is CVE-2012-1010?

CVE-2012-1010 is a high-severity vulnerability in n/a, published on 7 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in actions.php in the AllWebMenus plugin before 1.1.8 for WordPress allows remote attackers to execute arbitrary PHP code by uploading a ZIP file containing a PHP file, then accessing it via a direct request to the file in an unspecified directory.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Likno Allwebmenus Plugin.

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

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

## Is CVE-2012-1010 being exploited?

There is no known exploitation of CVE-2012-1010 in the wild and no public exploit code.

Public exploit code:

- WordPress Plugin AllWebMenus < 1.1.9 Menu Plugin - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-1011](https://insights.sbomify.com/CVE-2012-1011/): File upload in n/a (high 7.5)
- [CVE-2011-3981](https://insights.sbomify.com/CVE-2011-3981/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1010 is a high-severity vulnerability in n/a, published on 7 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1010 in the wild and no public exploit code.

Affected product: n/a. 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-1010/ (Markdown: https://insights.sbomify.com/CVE-2012-1010/index.md)
```

## Sources

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

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