iziModal Cross-site Scripting vulnerabilityGHSA-h685-83w4-3ph3
MEDIUMFix: marcelodolza/iziModal@01728acGHSA-h685-83w4-3ph3 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in izimodal. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for izimodal — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
izimodalnpmDescription
iziModal is a modal plugin with jQuery. Versions prior to 1.6.1 are vulnerable to cross-site scripting (XSS) when handling untrusted modal titles. An attacker who is able to influence the field title when creating a iziModal instance is able to supply arbitrary html or javascript code that will be rendered in the context of a user, potentially leading to XSS. Version 1.6.1 contains a patch for this issue
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | izimodal | all versions | 1.6.1npm install izimodal@1.6.1 |
Affected Products
izimodalizimodal_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for izimodal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update izimodal to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h685-83w4-3ph3 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-h685-83w4-3ph3 in your dependencies?
Find it across npm, including transitive dependencies.