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

> Authenticated users can upload malicious files disguised as images to execute arbitrary code on the server.

- **Severity:** Medium 6.5 (`AV:N/AC:L/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:** 17 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5j3c-768x-m8c6

## What is CVE-2012-2670?

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

### Official description

manageuser.php in Collabtive before 0.7.6 allows remote authenticated users, and possibly unauthenticated attackers, to bypass intended access restrictions and upload and execute arbitrary files by uploading an avatar file with an accepted Content-Type such as image/jpeg, then accessing it via a direct request to the file in files/standard/avatar.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: O-Dyn Collabtive.

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

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

## Is CVE-2012-2670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5027](https://insights.sbomify.com/CVE-2013-5027/): Missing authorization in n/a (critical 9.8)
- [CVE-2010-4269](https://insights.sbomify.com/CVE-2010-4269/): SQL injection in n/a (high 7.5)
- [CVE-2010-5285](https://insights.sbomify.com/CVE-2010-5285/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-3246](https://insights.sbomify.com/CVE-2014-3246/): SQL injection in n/a (medium 6.5)
- [CVE-2013-6872](https://insights.sbomify.com/CVE-2013-6872/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2670 is a medium-severity vulnerability in n/a, published on 17 Jun 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-2670 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-2670/ (Markdown: https://insights.sbomify.com/CVE-2012-2670/index.md)
```

## Sources

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

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