# CVE-2022-2111: Unrestricted Upload of File with Dangerous Type in inventree/inventree

> Attackers can upload dangerous file types to the InvenTree inventory system, potentially leading to remote code execution.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fr2w-mp56-g4xp, PYSEC-2026-825

## What is CVE-2022-2111?

CVE-2022-2111 is a critical vulnerability in inventree/inventree, published on 17 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Unrestricted Upload of File with Dangerous Type in GitHub repository inventree/inventree prior to 0.7.2.

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

## Which versions are affected by CVE-2022-2111?

3 open source packages ship an affected version, including inventree. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `inventree` | PyPI | All versions | 0.7.2 |
| `inventree` | PyPI | All versions | 0.7.2 |
| `inventree` | PyPI | All versions | 0.7.2 |

Products: Inventree Project Inventree.

## How do I fix CVE-2022-2111?

Upgrade inventree to 0.7.2 or later.

## Is CVE-2022-2111 being exploited?

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

## Other vulnerabilities in inventree/inventree

- [CVE-2022-2112](https://insights.sbomify.com/CVE-2022-2112/): Improper Neutralization of Formula Elements in a CSV File in inventree/inventree (critical 9.0)
- [CVE-2022-2113](https://insights.sbomify.com/CVE-2022-2113/): Cross-site Scripting (XSS) - Stored in inventree/inventree (high 8.4)
- [CVE-2026-35478](https://insights.sbomify.com/CVE-2026-35478/): InvenTree has Arbitrary API Token Creation (high 8.3)
- [CVE-2022-3355](https://insights.sbomify.com/CVE-2022-3355/): Cross-site Scripting (XSS) - Stored in inventree/inventree (high 8.2)
- [CVE-2026-33530](https://insights.sbomify.com/CVE-2026-33530/): InvenTree Vulnerable to ORM Filter Injection (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2111 and fix it if it is affected.

What it is: CVE-2022-2111 is a critical vulnerability in inventree/inventree, published on 17 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-2111 in the wild and no public exploit code.

Affected packages and fixed versions:
- inventree (PyPI): affected all versions; fixed in 0.7.2
- inventree (PyPI): affected all versions; fixed in 0.7.2
- inventree (PyPI): affected all versions; fixed in 0.7.2

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

## Sources

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

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