Highcharts Dashboards: editableOptions.propertyPath 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, 4.2.2
- 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 Dashboards, a charting component for JavaScript web applications, is affected when its edit mode processes configuration paths without filtering prototype-related keys. An attacker who can control those editable options could cause a value to be written onto the shared JavaScript Object.prototype, making it visible across the entire page and potentially altering application behavior.
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 1.0.0 until 4.2.2, Highcharts Dashboards edit mode walks editableOptions propertyPath segments without rejecting prototype-related keys. An attacker who controls editableOptions can provide a path through proto or constructor, and a user's edit writes the configured value onto Object.prototype. The property then becomes visible to JavaScript throughout the page, with consequences determined by the consuming application. This issue is fixed in 4.2.2.
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
fixed in 13.1.0
- @highcharts dashboards
From 1.0.0 · fixed in 4.2.2