<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 29 Oct 2026 23:40:57 +0000</lastBuildDate>
    <item>
      <title>GHSA-6hgp-fmhr-mrg4 — Highcharts Grid: `javascript:` URL in credits.href runs script on click</title>
      <link>https://db.gcve.eu/vuln/ghsa-6hgp-fmhr-mrg4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @highcharts/dashboards, npm: @highcharts/grid-pro&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### Workarounds
Paste in after the Grid Pro module is imported, before a Grid is created.&lt;/p&gt;
&lt;p&gt;```javascript
const { AST } = Grid;&lt;/p&gt;
&lt;p&gt;function sanitize(options) {
    const credits = options &amp;amp;&amp;amp; options.credits;&lt;/p&gt;
&lt;p&gt;if (credits &amp;amp;&amp;amp; typeof credits.href === &amp;#39;string&amp;#39;) {
        const filtered = AST.filterUserAttributes({ href: credits.href });&lt;/p&gt;
&lt;p&gt;if (!filtered.href) {
            delete credits.href;
        }
    }&lt;/p&gt;
&lt;p&gt;return options;
}&lt;/p&gt;
&lt;p&gt;// Both Grid.grid() and grid.update() funnel through loadUserOptions, so one
// hook covers both entry points.
const { prototype } = Grid.Grid;
const loadUserOptions = prototype.loadUserOptions;&lt;/p&gt;
&lt;p&gt;prototype.loadUserOptions = function (options, ...rest) {
    sanitize(options);
    return loadUserOptions.call(this, options, ...rest);
};
```&lt;/p&gt;
&lt;p&gt;### 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,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @highcharts/dashboards, npm: @highcharts/grid-pro&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### Workarounds
Paste in after the Grid Pro module is imported, before a Grid is created.&lt;/p&gt;
&lt;p&gt;```javascript
const { AST } = Grid;&lt;/p&gt;
&lt;p&gt;function sanitize(options) {
    const credits = options &amp;amp;&amp;amp; options.credits;&lt;/p&gt;
&lt;p&gt;if (credits &amp;amp;&amp;amp; typeof credits.href === &amp;#39;string&amp;#39;) {
        const filtered = AST.filterUserAttributes({ href: credits.href });&lt;/p&gt;
&lt;p&gt;if (!filtered.href) {
            delete credits.href;
        }
    }&lt;/p&gt;
&lt;p&gt;return options;
}&lt;/p&gt;
&lt;p&gt;// Both Grid.grid() and grid.update() funnel through loadUserOptions, so one
// hook covers both entry points.
const { prototype } = Grid.Grid;
const loadUserOptions = prototype.loadUserOptions;&lt;/p&gt;
&lt;p&gt;prototype.loadUserOptions = function (options, ...rest) {
    sanitize(options);
    return loadUserOptions.call(this, options, ...rest);
};
```&lt;/p&gt;
&lt;p&gt;### 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,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6hgp-fmhr-mrg4</guid>
    </item>
  </channel>
</rss>
