Highcharts: series column construction writes 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 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Highcharts JS, a JavaScript charting library used to build SVG charts in web pages, is affected in versions from 13.0.0 up to (but not including) 13.1.0. A crafted set of chart data can pollute the shared JavaScript object prototype on the page, which can disrupt chart rendering and change how other parts of the consuming application behave.
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 13.0.0 until 13.1.0, Highcharts builds series data columns by using point option keys directly as column IDs. Own enumerable proto and constructor keys from parsed point objects can therefore direct integer-indexed writes to Object.prototype or the Object constructor. The inherited values affect reads and for-in enumeration across the page and can disrupt rendering or alter consuming application behavior without user interaction beyond rendering the chart. This issue is fixed in 13.1.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- highcharts highcharts
From 13.0.0 · fixed in 13.1.0
- highchartsnpm
From 13.0.0 · fixed in 13.1.0