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

> Remote authors can execute arbitrary PHP code by uploading malicious files with double extensions in the Joomla JCE component when chunking is enabled.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2cqq-3cpj-9xcq

## What is CVE-2012-2902?

CVE-2012-2902 is a medium-severity vulnerability in n/a, published on 21 May 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in editor/extensions/browser/file.php in the Joomla Content Editor (JCE) component before 2.1 for Joomla!, when chunking is set to greater than zero, allows remote authors to execute arbitrary PHP code by uploading a PHP file with a double extension as demonstrated by .jpg.pht.

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

It affects 1 product.


Products: Ryan Demmer Joomla Content Editor.

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

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

## Is CVE-2012-2902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6419](https://insights.sbomify.com/CVE-2006-6419/): Path traversal in n/a (high 7.5)
- [CVE-2006-6420](https://insights.sbomify.com/CVE-2006-6420/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-6166](https://insights.sbomify.com/CVE-2006-6166/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2012-2901](https://insights.sbomify.com/CVE-2012-2901/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2902 is a medium-severity vulnerability in n/a, published on 21 May 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2902 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-2902/ (Markdown: https://insights.sbomify.com/CVE-2012-2902/index.md)
```

## Sources

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

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