GHSA-5GHW-9MGR-JVX2

Vulnerability from github – Published: 2026-10-28 19:56 – Updated: 2026-10-28 19:56
VLAI
Summary
Highcharts Grid Pro: cell-renderer `attributes` map written with raw `setAttribute`
Details

Impact

The input-type cell renderers copy every entry of the renderer's attributes option onto the input or select element they create, without checking the attribute names. An attacker who controls the Grid configuration can supply entries under a column's cells.renderer.attributes or cells.editMode.renderer.attributes whose names are event handlers, and those handlers execute in the origin of the page hosting the Grid. A view renderer places the handler on the input rendered in every row of the column as soon as the Grid renders; an edit-mode renderer places it on the input created when a cell enters edit mode, and that input is focused immediately, so a focus handler runs as soon as the user starts editing. Exploitation requires that untrusted data reach the Grid configuration and that a user hover over or focus one of the rendered inputs, or begin editing a cell. The Pro DataGrid that shipped inside the Dashboards package is included.

Workarounds

If your column configuration comes from a source you do not fully control, paste this snippet right after importing the Grid module:

const ALLOWED_RENDERER_ATTRIBUTES = [
    'autofocus', 'checked', 'max', 'maxlength', 'min', 'minlength',
    'multiple', 'pattern', 'placeholder', 'size', 'step'
];

const scrubColumn = (column) => {
    const cells = column?.cells;

    for (const renderer of [cells?.renderer, cells?.editMode?.renderer]) {
        const attributes = renderer?.attributes;

        if (attributes) {
            for (const key of Object.keys(attributes)) {
                if (!ALLOWED_RENDERER_ATTRIBUTES.includes(key.toLowerCase())) {
                    delete attributes[key];
                }
            }
        }
    }

    return column;
};

const scrubOptions = (options) => {
    scrubColumn(options?.columnDefaults);
    (options?.columns || []).forEach(scrubColumn);
    return options;
};

const proto = Grid.Grid.prototype;

const loadUserOptions = proto.loadUserOptions;
proto.loadUserOptions = function (options, ...rest) {
    scrubOptions(Grid.defaultOptions);
    return loadUserOptions.call(this, scrubOptions(options), ...rest);
};

const updateColumn = proto.updateColumn;
proto.updateColumn = function (columnId, options, ...rest) {
    return updateColumn.call(this, columnId, scrubColumn(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/grid-lite@3.2.0. If you load Highcharts Grid from a CDN, use a versioned URL, for example https://cdn.jsdelivr.net/npm/@highcharts/grid-lite@3.2.0/grid-lite.js. For more on each installation method, see the installation guide.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 3.1.0"
      },
      "package": {
        "ecosystem": "npm",
        "name": "@highcharts/grid-pro"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.0.0"
            },
            {
              "fixed": "3.2.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@highcharts/dashboards"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.6.0"
            },
            {
              "fixed": "4.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.6.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-116797"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-28T19:56:02Z",
    "nvd_published_at": "2026-10-28T18:17:14Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nThe input-type cell renderers copy every entry of the renderer\u0027s `attributes` option onto the input or select element they create, without checking the attribute names. An attacker who controls the Grid configuration can supply entries under a column\u0027s `cells.renderer.attributes` or `cells.editMode.renderer.attributes` whose names are event handlers, and those handlers execute in the origin of the page hosting the Grid. A view renderer places the handler on the input rendered in every row of the column as soon as the Grid renders; an edit-mode renderer places it on the input created when a cell enters edit mode, and that input is focused immediately, so a `focus` handler runs as soon as the user starts editing. Exploitation requires that untrusted data reach the Grid configuration and that a user hover over or focus one of the rendered inputs, or begin editing a cell. The Pro DataGrid that shipped inside the Dashboards package is included.\n\n### Workarounds\n\nIf your column configuration comes from a source you do not fully control, paste this snippet right after importing the `Grid` module:\n\n```ts\nconst ALLOWED_RENDERER_ATTRIBUTES = [\n    \u0027autofocus\u0027, \u0027checked\u0027, \u0027max\u0027, \u0027maxlength\u0027, \u0027min\u0027, \u0027minlength\u0027,\n    \u0027multiple\u0027, \u0027pattern\u0027, \u0027placeholder\u0027, \u0027size\u0027, \u0027step\u0027\n];\n\nconst scrubColumn = (column) =\u003e {\n    const cells = column?.cells;\n\n    for (const renderer of [cells?.renderer, cells?.editMode?.renderer]) {\n        const attributes = renderer?.attributes;\n\n        if (attributes) {\n            for (const key of Object.keys(attributes)) {\n                if (!ALLOWED_RENDERER_ATTRIBUTES.includes(key.toLowerCase())) {\n                    delete attributes[key];\n                }\n            }\n        }\n    }\n\n    return column;\n};\n\nconst scrubOptions = (options) =\u003e {\n    scrubColumn(options?.columnDefaults);\n    (options?.columns || []).forEach(scrubColumn);\n    return options;\n};\n\nconst proto = Grid.Grid.prototype;\n\nconst loadUserOptions = proto.loadUserOptions;\nproto.loadUserOptions = function (options, ...rest) {\n    scrubOptions(Grid.defaultOptions);\n    return loadUserOptions.call(this, scrubOptions(options), ...rest);\n};\n\nconst updateColumn = proto.updateColumn;\nproto.updateColumn = function (columnId, options, ...rest) {\n    return updateColumn.call(this, columnId, scrubColumn(options), ...rest);\n};\n```\n\n### Obtaining the patched version\nThe 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/grid-lite@3.2.0`. If you load Highcharts Grid from a CDN, use a versioned URL, for example `https://cdn.jsdelivr.net/npm/@highcharts/grid-lite@3.2.0/grid-lite.js`. For more on each installation method, see the [installation guide](https://www.highcharts.com/docs/grid/installation).",
  "id": "GHSA-5ghw-9mgr-jvx2",
  "modified": "2026-10-28T19:56:03Z",
  "published": "2026-10-28T19:56:02Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/highcharts/highcharts/security/advisories/GHSA-5ghw-9mgr-jvx2"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116797"
    },
    {
      "type": "WEB",
      "url": "https://github.com/highcharts/highcharts/commit/52abd4f8f8db87dd20eab7c01444112380e30e98"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/highcharts/highcharts"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Highcharts Grid Pro: cell-renderer `attributes` map written with raw `setAttribute`"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.