GHSA-2P49-HGCM-8545

SVGO removeScripts plugin leaves some executable scripts intact

import { optimize } from 'svgo';

/** Presume that this string was obtained in some other way, such as network. */
const original = `
  <svg xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" xmlns:uwu="http://www.w3.org/1999/xlink" viewBox="0 0 100 100" version="1.1">
    <a uwu:href="JavaScript:(() =&gt; { alert(document.cookie) })();"><text y="30">uwu</text></a>
    <svg:script>
      alert(document.cookie);
    </svg:script>
  </svg>
`;

optimize(original, {
  plugins: ['removeScripts']
});
// Did not remove <svg:script> or uwu:href="JavaScript:…, still executed by browsers.

yarn up svgo

# or if SVGO is a nested dependency
yarn up -R svgo

If you run SVGO on untrusted input (e.g., user uploads to a web application) and you depended on removeScripts, then some scripts may still be present. If that SVG was then opened directly by another user on the same domain, it could invoke scripts that could read local storage or cookies.

This may affect you if you have enabled one of the following:

It's unlikely to impact users who just use SVGO locally on their own SVGs or in build pipelines.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

GHSA-2P49-HGCM-8545 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.3, 3.3.4, 4.0.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-2P49-HGCM-8545? GHSA-2P49-HGCM-8545 is a high-severity cross-site scripting (XSS) vulnerability in svgo (npm), affecting versions >= 1.0.0, < 2.8.3. It is fixed in 2.8.3, 3.3.4, 4.0.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-2P49-HGCM-8545? GHSA-2P49-HGCM-8545 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of svgo are affected by GHSA-2P49-HGCM-8545? svgo (npm) versions >= 1.0.0, < 2.8.3 is affected.
4. Is there a fix for GHSA-2P49-HGCM-8545? Yes. GHSA-2P49-HGCM-8545 is fixed in 2.8.3, 3.3.4, 4.0.2. Upgrade to this version or later.
5. Is GHSA-2P49-HGCM-8545 exploitable, and should I be worried? Whether GHSA-2P49-HGCM-8545 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-2P49-HGCM-8545 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-2P49-HGCM-8545?
   • Upgrade svgo to 2.8.3 or later
   • Upgrade svgo to 3.3.4 or later
   • Upgrade svgo to 4.0.2 or later

Other vulnerabilities in svgo