Typemill SvgSanitizer.php saveImage cross site scripting
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 35/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Typemill, a flat-file content management system, is affected by a cross-site scripting flaw in its SVG image upload handling, which fails to properly sanitize malicious content. An attacker could exploit this remotely to run harmful scripts in users' browsers, potentially compromising their sessions or data.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
Typemill SVG file uploads are processed by the SVG sanitizerApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n/a Typemill
2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14, 2.15, 2.16, 2.17, 2.18, 2.19, 2.20, 2.21, 2.22, 2.23, 2.24, 2.25, 2.26.0
Evidence 8
- Advisory
- Advisory
- Advisory
- Advisory
- Patch
- Patch
- Exploit
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120218
What does this mean?
The Typemill SVG sanitizer did not remove processing instructions and comments from uploaded SVG files. Its hardening against stored cross-site scripting adds their removal, so the flaw allowed script-carrying content to be stored through SVG uploads.Source: github.com
Am I affected, and how do I check?
The checked facts name Typemill with no version ranges, so the affected versions are not stated. The relevant setup is an installation that accepts SVG uploads through the SvgSanitizer.php saveImage path, and the Typemill version can be checked in the project's release notes or installed package.Source: github.com
What should I do about it?
The checked facts do not name a fixed version. Check the Typemill release notes for a release that includes the SVG sanitizer hardening against stored XSS.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data