Highcharts Core: AST `DOMParser` fallback assigns unsanitized markup to `innerHTML` during print
- Published
- 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
- Fix
- Fixed in 12.6.1, 13.1.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Highcharts Core, the JavaScript charting library (including its Stock, Maps, and Gantt products), is affected. An attacker who can supply untrusted text options, such as chart titles or labels, can get malicious scripts to run in the hosting page's origin when the chart is printed.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Highcharts JS is a JavaScript charting library based on SVG. From 12.0.0 until 12.6.1 and 13.1.0, Highcharts falls back to assigning raw markup to innerHTML when DOMParser cannot return a document, before its allow-list is applied. In Chromium, the Trusted Types callback can throw while a beforeprint handler runs, so a page that redraws a chart during beforeprint can insert untrusted HTML text options into the hosting document. Event handlers in that markup then run in the page origin when printing begins. The issue affects HTML-rendered titles, labels, data labels, responsive text, and the Stock, Maps, and Gantt products shipped in the same package. This issue is fixed in 12.6.1 and 13.1.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- highcharts highcharts
From 12.0.0 · fixed in 12.6.1; From 13.0.0 · fixed in 13.1.0
- highchartsnpm
From 12.0.0 · fixed in 12.6.1
- highchartsnpm
From 13.0.0 · fixed in 13.1.0