Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

Potential XSS in jQuery dependency in MiradorGHSA-hgwm-pv9h-q5m7

GHSA-hgwm-pv9h-q5m7 is a security vulnerability in mirador. A fix is available for mirador — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 4, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
miradornpm
7Kdownloads / week

Description

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.

Patches

Mirador adopters should update to v3.0.0, no updates exist for v2.x releases.

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/

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmiradorall versions3.0.0-alpha.0npm install mirador@3.0.0-alpha.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mirador, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update mirador to 3.0.0-alpha.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hgwm-pv9h-q5m7 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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. ### Patches Mirador adopters should update to v3.0.0, no updates exist for v2.x releases. ### 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
O3 Security · Impact-Aware SCA

Is GHSA-hgwm-pv9h-q5m7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Potential XSS in jQuery dependency in Mirador