Summary
Potential XSS in jQuery dependency in Mirador
Workarounds
Yes, Mirador users could fork and create their own custom build of Mirador and make the bug fixes themselves.
References
https://github.com/advisories/GHSA-gxr4-xjj5-5px2
https://github.com/advisories/GHSA-jpcq-cgw6-v4j6
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
https://jquery.com/upgrade-guide/3.5/
Impact
Mirador users less than v3.0.0 (alpha-rc) versions that have an unpatched jQuery. When adopters update jQuery they will find some of Mirador functionality to be broken.
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
Mirador adopters should update to v3.0.0, no updates exist for v2.x releases.
Frequently Asked Questions
- What is GHSA-HGWM-PV9H-Q5M7? GHSA-HGWM-PV9H-Q5M7 is a medium-severity cross-site scripting (XSS) vulnerability in mirador (npm), affecting versions <= 2.7.2. It is fixed in 3.0.0-alpha.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of mirador are affected by GHSA-HGWM-PV9H-Q5M7? mirador (npm) versions <= 2.7.2 is affected.
- Is there a fix for GHSA-HGWM-PV9H-Q5M7? Yes. GHSA-HGWM-PV9H-Q5M7 is fixed in 3.0.0-alpha.0. Upgrade to this version or later.
- Is GHSA-HGWM-PV9H-Q5M7 exploitable, and should I be worried? Whether GHSA-HGWM-PV9H-Q5M7 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-HGWM-PV9H-Q5M7 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-HGWM-PV9H-Q5M7? Upgrade
miradorto 3.0.0-alpha.0 or later.