Highcharts: dotted series.keys paths write to Object.prototype
- 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 11.4.9, 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, a JavaScript charting library used in web pages, is affected. An attacker who can control chart series configuration and matching data can cause arbitrary properties to be added to Object.prototype, which then become visible to all JavaScript running on the page.
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 6.1.0 until 11.4.9, 12.6.1, and 3.1.0, Highcharts follows dot-separated series.keys paths without filtering each segment. An attacker who controls series.keys and matching point data can use a path through proto to assign arbitrary named properties to Object.prototype. Those properties are visible to all JavaScript in the page, and no user interaction is required beyond rendering the chart. This issue is fixed in 11.4.9, 12.6.1, and 3.1.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- highcharts highcharts
From 6.1.0 · fixed in 11.4.9; 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
- highchartsnpm
From 6.1.0 · fixed in 11.4.9