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

> Remote attackers can execute arbitrary code by uploading malicious files to the RBX Gallery WordPress plugin without authentication.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cgw2-cwh6-c7wv

## What is CVE-2012-3575?

CVE-2012-3575 is a critical vulnerability in n/a, published on 16 Jun 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 uploader.php in the RBX Gallery plugin 2.1 for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in uploads/rbxslider.

Weakness: CWE-264

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

It affects 1 product.


Products: Rbx Gallery Rbx Gallery.

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

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

## Is CVE-2012-3575 being exploited?

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

Public exploit code:

- WordPress Plugin RBX Gallery 2.1 - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3575 is a critical vulnerability in n/a, published on 16 Jun 2012. 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-3575 exists.

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-3575/ (Markdown: https://insights.sbomify.com/CVE-2012-3575/index.md)
```

## Sources

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

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