GHSA-grj7-r4jv-pw9j: XSS

Published Oct 28, 2026
·
Updated

Impact The Highcharts component uses the value of chartConstructor to select a function from the Highcharts namespace and invokes it with the component's container element and its chartOptions, without checking the value against the supported chart constructors. An attacker who controls the dashboard configuration can therefore name any other public member of that namespace; utility functions in that namespace copy the supplied options onto the container element as properties or attributes, so markup and event handlers carried in chartOptions land in the page and run in the origin of the page hosting the dashboard. Exploitation requires that untrusted data reach the Dashboards component configuration. No user interaction is required beyond rendering the board.

Workarounds If your board configuration comes from a source you do not fully control, paste this snippet right after importing libraries: ts (function () { const HighchartsComponent = Dashboards && Dashboards.HighchartsComponent;

if (!HighchartsComponent || !HighchartsComponent.prototype.createChart) { return; // HighchartsComponent not loaded }

const allowedConstructors = [ 'chart', 'stockChart', 'mapChart', 'ganttChart' ]; const originalCreateChart = HighchartsComponent.prototype.createChart;

HighchartsComponent.prototype.createChart = function () { if (allowedConstructors.indexOf(this.chartConstructor) === -1) { this.chartConstructor = 'chart'; }

return originalCreateChart.apply(this, arguments); }; }());

Obtaining the patched version The patched releases are available from all the usual distribution channels. With npm, upgrade the affected package to the patched version listed above, for example npm install @highcharts/dashboards@4.2.2. If you load Highcharts Dashboards from a CDN, use a versioned URL, for example https://code.highcharts.com/dashboards/4.2.2/dashboards.js. For more on each installation method, see the installation guide.

Affected Software

1 affected componentFixes available
npm/@highcharts/dashboards>=1.0.0<=4.2.1
4.2.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@highcharts/dashboards to a version that resolves this vulnerability.

    Fixed in 4.2.2
  2. Upgrade

    Upgrade @highcharts/dashboards to a version that resolves this vulnerability.

    Fixed in 4.2.2
  3. Compensating control

    For board configurations from sources you do not fully control, restrict HighchartsComponent chartConstructor to the allowed constructors 'chart', 'ganttChart', 'mapChart', and 'stockChart'; if the value is not allowed, set chartConstructor to 'chart' before rendering.

Event History

Oct 28, 2026
Advisory Published
via GitHub·07:55 PM
Data Sourced
via GitHub·07:55 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Dashboards that allow untrusted parties to supply or influence the Highcharts component configuration are exposed. Boards whose configuration comes only from a fully trusted source are not described as exploitable by the advisory.

2

What does an attacker need to exploit it?

An attacker needs control over data that reaches the Dashboards component configuration, including the chartConstructor value and chartOptions. No user interaction is required after the board renders.

3

What can be done if patching is not immediately possible?

Apply the provided workaround immediately after importing the libraries. It replaces createChart behavior so that chartConstructor is limited to chart, stockChart, and mapChart.

4

What is the impact of successful exploitation?

An attacker can cause markup and event handlers supplied in chartOptions to be placed on the page. Those handlers execute in the origin of the page hosting the dashboard.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203