Potential XSS in jQuery dependency in Mirador
Summary
GHSA-hgwm-pv9h-q5m7: Potential XSS in jQuery dependency in Mirador. Affects mirador versions < 3.0.0-alpha.0. Fixed in 3.0.0-alpha.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Mirador is an open-source viewer and annotation tool for displaying, comparing, and manipulating multiple images. It is commonly used in digital humanities projects and cultural heritage institutions. The vulnerability affects Mirador versions prior to v3.0.0 (alpha-rc) that have an unpatched jQuery.
Vulnerability Detail
The vulnerability in Mirador is a potential cross-site scripting (XSS) issue. It arises from the use of an outdated and unpatched version of jQuery. When Mirador adopters update jQuery, they may encounter broken functionality in their applications. This vulnerability can be exploited by an attacker to inject malicious scripts into web pages viewed by users of the affected Mirador versions.
How To Fix
Latest published version: 4.3.0 as of 23 Oct 2026
npm install mirador@4.3.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.0.0-alpha.0
This is the first release that contains the fix.
npm install mirador@3.0.0-alpha.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
Mirador users have the option to fork the project and create their own custom build of Mirador. By doing so, they can make the necessary bug fixes themselves and mitigate the XSS vulnerability. However, this workaround requires technical expertise and ongoing maintenance to keep the custom build up to date with future releases of Mirador.
Conclusion
The potential XSS vulnerability in Mirador can be mitigated by updating to v3.0.0 or later. Mirador adopters should ensure that their installations are running the latest version to protect against this security risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for mirador →
FAQ
Mirador is an open-source viewer and annotation tool for displaying, comparing, and manipulating multiple images. It is commonly used in digital humanities projects and cultural heritage institutions.
Mirador versions prior to v3.0.0 (alpha-rc) are affected by this vulnerability. Specifically, versions up to and including v2.7.2 are vulnerable.
The vulnerability can allow an attacker to inject malicious scripts into web pages viewed by users of the affected Mirador versions. This can lead to various security risks, including unauthorized access to user data or the execution of arbitrary code.
To fix the vulnerability, you should update your Mirador installation to v3.0.0 or later. This will ensure that the jQuery dependency is patched and protected against XSS attacks.
Yes, you can fork the Mirador project and create your own custom build. By doing so, you can make the necessary bug fixes to mitigate the XSS vulnerability. However, this workaround requires technical expertise and ongoing maintenance.
