# CVE-2026-120218: Typemill SvgSanitizer.php saveImage cross site scripting


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-wh4p-gf4j-mjqc

## What is CVE-2026-120218?

CVE-2026-120218 is a medium-severity vulnerability in Typemill, published on 1 Nov 2026. 

### Official description

A flaw has been found in Typemill up to 2.26.0. The impacted element is the function ControllerApiImage::saveImage of the file system/typemill/Models/SvgSanitizer.php. Executing a manipulation can lead to cross site scripting. The attack may be performed from remote. The exploit has been published and may be used. Upgrading to version 2.27.0 is sufficient to resolve this issue. This patch is called 9ca43c4a7b6764c5a6ac11a2ccc099b036ee3cef. It is recommended to upgrade the affected component.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-120218?


## How do I fix CVE-2026-120218?

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

## Is CVE-2026-120218 being exploited?

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

Public exploit code:

- CVE-2026-120218: bilingual TypeMill stored XSS analysis and safe SVG/XSLT PoC (github_poc): https://github.com/capivara-research/CVE-2026-120218

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120218 and fix it if it is affected.

What it is: CVE-2026-120218 is a medium-severity vulnerability in Typemill, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120218 exists.

Affected product: Typemill. 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-2026-120218/ (Markdown: https://insights.sbomify.com/CVE-2026-120218/index.md)
```

## Sources

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

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