<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-29T23:40:57.535915+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6hgp-fmhr-mrg4</id>
    <title>GHSA-6hgp-fmhr-mrg4 — Highcharts Grid: `javascript:` URL in credits.href runs script on click</title>
    <updated>2026-10-29T23:40:57.537614+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @highcharts/dashboards, npm: @highcharts/grid-pro</p>
<p>### 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.</p>
<p>### Workarounds
Paste in after the Grid Pro module is imported, before a Grid is created.</p>
<p>```javascript
const { AST } = Grid;</p>
<p>function sanitize(options) {
    const credits = options &amp;&amp; options.credits;</p>
<p>if (credits &amp;&amp; typeof credits.href === 'string') {
        const filtered = AST.filterUserAttributes({ href: credits.href });</p>
<p>if (!filtered.href) {
            delete credits.href;
        }
    }</p>
<p>return options;
}</p>
<p>// Both Grid.grid() and grid.update() funnel through loadUserOptions, so one
// hook covers both entry points.
const { prototype } = Grid.Grid;
const loadUserOptions = prototype.loadUserOptions;</p>
<p>prototype.loadUserOptions = function (options, ...rest) {
    sanitize(options);
    return loadUserOptions.call(this, options, ...rest);
};
```</p>
<p>### 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,…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6hgp-fmhr-mrg4"/>
  </entry>
</feed>
