# CVE-2022-3355: Cross-site Scripting (XSS) - Stored in inventree/inventree

> Attackers can inject malicious scripts into InvenTree, potentially executing code or hijacking user accounts.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-62g7-fpv9-v95f, PYSEC-2026-823

## What is CVE-2022-3355?

CVE-2022-3355 is a high-severity cross-site scripting vulnerability in inventree/inventree, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross-site Scripting (XSS) - Stored in GitHub repository inventree/inventree prior to 0.8.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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


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

Products: Inventree Project Inventree.

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

Upgrade inventree to 0.8.3 or later.

## Is CVE-2022-3355 being exploited?

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

## Other vulnerabilities in inventree/inventree

- [CVE-2022-2111](https://insights.sbomify.com/CVE-2022-2111/): Unrestricted Upload of File with Dangerous Type in inventree/inventree (critical 9.0)
- [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-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-3355 and fix it if it is affected.

What it is: CVE-2022-3355 is a high-severity cross-site scripting vulnerability in inventree/inventree, published on 29 Sep 2022. 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-2022-3355 exists.

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

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

## Sources

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

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