p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in @highcharts/grid-pro

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für @highcharts/grid-pro: 5. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 5

  1. CVE-2026-118255

    Hoch · CVSS 8.4EPSS 0,35%Korrektur verfügbar

    Highcharts Grid: javascript: URL in credits.href runs script on click

    Highcharts JS is a JavaScript charting library based on SVG. From 2.0.0 until 3.2.0, Highcharts Grid applies credits.href to the credits link without validating the URL scheme. An attacker who controls Grid configuration can provide a javascript URL, and activating the credits link runs script in the origin of the hosting page with access to that application's data and session state.This issue is fixed in Grid Pro 3.2.0.

    • Auf 3.2.0 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-118254

    Hoch · CVSS 8.6EPSS 0,42%Korrektur verfügbar

    Highcharts Grid: pagination language options are parsed as HTML

    Highcharts JS is a JavaScript charting library based on SVG. From 2.0.0 until 3.2.0, Highcharts Grid writes pagination language strings into the DOM as markup instead of text. An attacker who controls the Grid language configuration can provide elements with event handlers, which execute in the hosting page origin when pagination controls render. Exploitation requires pagination to be enabled but does not require additional user interaction. This issue is fixed in 3.2.0.

    • Auf 3.2.0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-118247

    Mittel · CVSS 6.9EPSS 0,36%Korrektur verfügbar

    Highcharts Dashboards / Grid Pro: `DataTable.setCell` and column writers treat `__proto__` as an existing column.

    Highcharts JS is a JavaScript charting library based on SVG. From 1.0.0 until Dashboards 4.2.2, and from 2.0.0 until Grid Pro 3.2.0, Highcharts DataTable single-cell writers use an untrusted column ID as a key without rejecting __proto__ or constructor. DataTable.setCell, including Dashboards connector write-back and Grid Pro editing paths, can therefore write integer-indexed values onto Object.prototype or the Object constructor. In Dashboards releases with column aliases, a literal __proto__ ID is redirected by the alias map, while an alias targeting __proto__ reaches the unsafe write; later releases without aliases accept the unsafe ID dir

    • Auf 3.2.0 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-118242

    Hoch · CVSS 8.5EPSS 0,3%Korrektur verfügbar

    Highcharts Grid: custom icon definition objects written with raw `setAttribute` on `<path>`

    Highcharts JS is a JavaScript charting library based on SVG. From 2.3.0 until 3.2.0, Highcharts Grid creates SVG path elements from rendering.icons object definitions and previously copied every child key with setAttribute. An attacker who controls Grid configuration can supply event-handler attribute names in an icon definition. Because custom icons override built-ins, the attacker can replace default sort or pagination icons, and script runs in the hosting page origin when a user hovers over or activates the affected icon. This issue is fixed in 3.2.0.

    • Auf 3.2.0 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-116797

    Hoch · CVSS 8.5EPSS 0,32%Korrektur verfügbar

    Highcharts Grid Pro: cell-renderer `attributes` map written with raw `setAttribute`

    Highcharts JS is a JavaScript charting library based on SVG. From 2.0.0 until 3.2.0, Highcharts Grid Pro input renderers copy the cells.renderer.attributes and cells.editMode.renderer.attributes maps to input or select elements with raw setAttribute calls. An attacker who controls column configuration can add event-handler attributes to every rendered row or to the control created when a cell enters edit mode. Script then runs in the hosting page origin when a user hovers over or focuses an input or begins editing. This issue is fixed in Grid Pro 3.2.0.

    • Auf 3.2.0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →