Summary
Cross-Site Scripting in google-closure-library
Versions of google-closure-library prior to 20190301.0.0 are vulnerable to Cross-Site Scripting. The safedomtreeprocessor.processToString() function improperly processed empty elements, which could allow attackers to execute arbitrary JavaScript through Mutation Cross-Site Scripting.
Impact
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to version 20190301.0.0 or later.
Frequently Asked Questions
- What is GHSA-R9Q4-W3FM-WRM2? GHSA-R9Q4-W3FM-WRM2 is a medium-severity cross-site scripting (XSS) vulnerability in google-closure-library (npm), affecting versions < 20190301.0.0. It is fixed in 20190301.0.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of google-closure-library are affected by GHSA-R9Q4-W3FM-WRM2? google-closure-library (npm) versions < 20190301.0.0 is affected.
- Is there a fix for GHSA-R9Q4-W3FM-WRM2? Yes. GHSA-R9Q4-W3FM-WRM2 is fixed in 20190301.0.0. Upgrade to this version or later.
- Is GHSA-R9Q4-W3FM-WRM2 exploitable, and should I be worried? Whether GHSA-R9Q4-W3FM-WRM2 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
- What actually determines whether GHSA-R9Q4-W3FM-WRM2 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.
- How do I fix GHSA-R9Q4-W3FM-WRM2? Upgrade
google-closure-libraryto 20190301.0.0 or later.