# CVE-2022-3607: Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in octoprint/octoprint

> Attackers can inject special elements into OctoPrint, potentially leading to code execution or account takeover via cross-site scripting.

- **Severity:** Medium 6.0 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2022
- **Updated:** 9 May 2025
- **Also known as:** GHSA-rj5f-vm79-5j84, PYSEC-2022-42975

## What is CVE-2022-3607?

CVE-2022-3607 is a medium-severity cross-site scripting vulnerability in octoprint/octoprint, published on 19 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in GitHub repository octoprint/octoprint prior to 1.8.3.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-75 (Failure to Sanitize Special Elements into a Different Plane)

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

3 open source packages ship an affected version, including octoprint and OctoPrint. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `octoprint` | PyPI | All versions | 1.8.3 |
| `octoprint` | PyPI | All versions | 1.8.3 |
| `OctoPrint` | PyPI | All versions | 1.8.3 |

Products: Octoprint Octoprint.

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

Upgrade octoprint to 1.8.3 or later.

## Is CVE-2022-3607 being exploited?

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

## Other vulnerabilities in octoprint/octoprint

- [CVE-2018-16710](https://insights.sbomify.com/CVE-2018-16710/): Information disclosure in n/a (critical 9.1)
- [CVE-2025-58180](https://insights.sbomify.com/CVE-2025-58180/): OctoPrint is Vulnerable to RCE Attacks via Unsanitized Filename in File Upload (high 7.5)
- [CVE-2022-1430](https://insights.sbomify.com/CVE-2022-1430/): Cross-site Scripting (XSS) - DOM in octoprint/octoprint (high 7.5)
- [CVE-2022-1432](https://insights.sbomify.com/CVE-2022-1432/): Cross-site Scripting (XSS) - Generic in octoprint/octoprint (high 7.5)
- [CVE-2024-32977](https://insights.sbomify.com/CVE-2024-32977/): OctoPrint Authentication Bypass via X-Forwarded-For Header when autologinLocal is enabled (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3607 is a medium-severity cross-site scripting vulnerability in octoprint/octoprint, published on 19 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3607 exists.

Affected packages and fixed versions:
- octoprint (PyPI): affected all versions; fixed in 1.8.3
- octoprint (PyPI): affected all versions; fixed in 1.8.3
- OctoPrint (PyPI): affected all versions; fixed in 1.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-3607/ (Markdown: https://insights.sbomify.com/CVE-2022-3607/index.md)
```

## Sources

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

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