NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-118255: Highcharts Grid: `javascript:` URL in credits.href runs script on click

highCVSS 4.0 8.4GHSA-6hgp-fmhr-mrg4

Highcharts Grid does not check the scheme of `credits.href`. An attacker who controls the Grid configuration can set a `javascript:` URL, and clicking the credits link runs the script in the hosting page. The advisory lists `@highcharts/grid-pro` 2.0.0 through 3.1.0 (fixed in 3.2.0) and `@highcharts/dashboards` 3.2.0 through 3.6.0 (fixed in 4.0.0).

Published Oct 28, 2026 · Analysis Nov 1, 2026

What an attacker can do

The credits.href option is applied to the credits link without a check against an allowed-scheme list. A value that starts with javascript: therefore runs when someone activates the link, in the origin of the page that hosts the Grid.

Two conditions must hold. Untrusted data must reach the Grid configuration, for example options assembled from user-supplied or stored JSON. A user must then activate the credits link. The CVSS 4.0 vector marks this PR:L and UI:A.

The script has the same access to page data, storage and session state as the host application. It can read what the Grid shows, call the application's APIs as the signed-in user and take tokens from browser storage. Grids with hard-coded options give an attacker no route in.

The advisory's workaround shows the entry points: Grid.grid() and grid.update() both go through loadUserOptions, so one hook on that method covers both. It uses AST.filterUserAttributes to drop a credits.href that does not pass the filter.

This is the Grid counterpart of the core highcharts credits.href flaw, CVE-2026-118251.

Who is affected

Per the advisory data: npm @highcharts/grid-pro from 2.0.0 through 3.1.0, and @highcharts/dashboards from 3.2.0 through 3.6.0. Exposure needs untrusted input in the Grid configuration. The advisory's install example names @highcharts/grid-lite, but that package is not in the listed ranges, so confirm with the vendor if you use it.

npm ls @highcharts/grid-pro @highcharts/dashboards

@highcharts/dashboards

Ecosystem
npm
Affected
>= 3.2.0, <= 3.6.0
Fixed in
4.0.0
Check
npm ls @highcharts/dashboards

@highcharts/grid-pro

Ecosystem
npm
Affected
>= 2.0.0, <= 3.1.0
Fixed in
3.2.0
Check
npm ls @highcharts/grid-pro

How to fix it

Upgrade @highcharts/grid-pro to 3.2.0 and @highcharts/dashboards to 4.0.0.

npm install @highcharts/[email protected]
npm install @highcharts/[email protected]

CDN users can pin a versioned URL, for example one under cdn.jsdelivr.net/npm for the package version.

Workaround from the advisory: after the Grid Pro module is imported and before any Grid is created, wrap Grid.Grid.prototype.loadUserOptions so it passes credits.href through AST.filterUserAttributes and deletes the value if it is filtered out. The advisory has the full snippet.

How to tell if you were hit

Search stored Grid configurations, API payloads and database fields for a credits object whose href begins with javascript:, in any letter case. Review code paths that merge user input into Grid options. Check server logs for requests that save configuration containing javascript:. Check the browser console on a patched version for rejected attributes.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Impact

An attacker who controls the Grid configuration can set credits.href to a javascript: URL. The value is not validated against an allowed-scheme list before it is applied to the credits link, so activating that link runs attacker-supplied script in the origin of the page hosting the Grid. Exploitation requires that untrusted data reach the Grid configuration and that a user activate the credits link. Script running this way has the same access to page data, storage and session state as the hosting application.

Workarounds

Paste in after the Grid Pro module is imported, before a Grid is created.

const { AST } = Grid;

function sanitize(options) {
    const credits = options && options.credits;

    if (credits && typeof credits.href === 'string') {
        const filtered = AST.filterUserAttributes({ href: credits.href });

        if (!filtered.href) {
            delete credits.href;
        }
    }

    return options;
}

// Both Grid.grid() and grid.update() funnel through loadUserOptions, so one
// hook covers both entry points.
const { prototype } = Grid.Grid;
const loadUserOptions = prototype.loadUserOptions;

prototype.loadUserOptions = function (options, ...rest) {
    sanitize(options);
    return loadUserOptions.call(this, options, ...rest);
};

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/[email protected]. If you load Highcharts Grid from a CDN, use a versioned URL, for example https://cdn.jsdelivr.net/npm/@highcharts/[email protected]/grid-lite.js. For more on each installation method, see the installation guide.

Questions

Does CVE-2026-118255 need user interaction?

Yes. A user has to activate the credits link, and the attacker must be able to put a value into the Grid configuration.

Which packages and versions does it cover?

@highcharts/grid-pro 2.0.0 to 3.1.0, fixed in 3.2.0, and @highcharts/dashboards 3.2.0 to 3.6.0, fixed in 4.0.0.

Is this the same as the core Highcharts credits.href issue?

It is the same kind of flaw in the Grid code. The core highcharts package has its own advisory, CVE-2026-118251, with different packages and fixed versions.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More npm vulnerabilities

All npm entries