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

> Remote attackers can upload malicious files to execute arbitrary code or read sensitive data in Invision Power Board.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h7fh-8x45-4h5p

## What is CVE-2012-2226?

CVE-2012-2226 is a critical vulnerability in n/a, published on 9 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Invision Power Board before 3.3.1 fails to sanitize user-supplied input which could allow remote attackers to obtain sensitive information or execute arbitrary code by uploading a malicious file.

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

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

It affects 1 product.


Products: Invisioncommunity Invision Power Board.

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

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

## Is CVE-2012-2226 being exploited?

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

Public exploit code:

- Invision Power Board 3.3.0 - Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-5692](https://insights.sbomify.com/CVE-2012-5692/): Other in n/a (critical 10.0)
- [CVE-2013-3725](https://insights.sbomify.com/CVE-2013-3725/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-8898](https://insights.sbomify.com/CVE-2017-8898/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2014-4928](https://insights.sbomify.com/CVE-2014-4928/): SQL injection in n/a (high 8.8)
- [CVE-2017-8899](https://insights.sbomify.com/CVE-2017-8899/): Cross-site scripting in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2226 is a critical vulnerability in n/a, published on 9 Jan 2020. 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-2226 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-2226/ (Markdown: https://insights.sbomify.com/CVE-2012-2226/index.md)
```

## Sources

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

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