GHSA-9v3m-8fp8-mj99 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.webjars:bootstrap. 4 public exploit references exist, so weaponization risk is real. A fix is available for org.webjars:bootstrap — see the affected versions and patch details below.
Bootstrap Vulnerable to Cross-Site Scripting
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-9v3m-8fp8-mj99 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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.
bootstrapnpmDescription
Versions of bootstrap prior to 3.4.1 for 3.x and 4.3.1 for 4.x are vulnerable to Cross-Site Scripting (XSS). The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.
Recommendation
For bootstrap 4.x upgrade to 4.3.1 or later.
For bootstrap 3.x upgrade to 3.4.1 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars:bootstrap | ≥ 3.0.0&&< 3.4.1 | 3.4.1org.webjars:bootstrap:3.4.1 |
| ☕Maven | org.webjars:bootstrap | ≥ 4.0.0&&< 4.3.1 | 4.3.1org.webjars:bootstrap:4.3.1 |
| 📦npm | bootstrap | ≥ 4.0.0&&< 4.3.1 | 4.3.1npm install bootstrap@4.3.1 |
| 📦npm | bootstrap | ≥ 3.0.0&&< 3.4.1 | 3.4.1npm install bootstrap@3.4.1 |
| 📦npm | bootstrap-sass | ≥ 3.0.0&&< 3.4.1 | 3.4.1npm install bootstrap-sass@3.4.1 |
| .NETNuGet | Bootstrap.Less | ≥ 3.0.0&&< 3.4.1 | 3.4.1dotnet add package Bootstrap.Less --version 3.4.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the…
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the…
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars:bootstrap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.webjars:bootstrap to 3.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9v3m-8fp8-mj99 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9v3m-8fp8-mj99 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9v3m-8fp8-mj99. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat CloudForms 4.6 and newer versions include the vulnerable component, but there is no risk of exploitation since there is no possible vector to access the vulnerability. Older Red Hat CloudForms versions don't use the vulnerable component at all.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 7 | ipa-0:4.6.8-5.el7 | RHSA-2020:3936 |
| Red Hat Enterprise Linux 8 | idm:client-8030020200923172426.05ac3f11 | RHSA-2020:4670 |
| Red Hat Enterprise Linux 8 | pki-core:10.6-8030020200911215836.5ff1562f | RHSA-2020:4847 |
| Red Hat Fuse 7.11.1 | io.hawt-hawtio-online | RHSA-2022:8652 |
| Red Hat JBoss Enterprise Application Platform 7.4.9 | org.jboss.hal/hal-console:3.3.16.Final-redhat-00001 | RHSA-2023:0556 |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | eap7-hal-console-0:3.3.16-1.Final_redhat_00001.1.el8eap | RHSA-2023:0553 |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9 | eap7-hal-console-0:3.3.16-1.Final_redhat_00001.1.el9eap | RHSA-2023:0554 |
| Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 | eap7-hal-console-0:3.3.16-1.Final_redhat_00001.1.el7eap | RHSA-2023:0552 |
Frequently Asked Questions
Is GHSA-9v3m-8fp8-mj99 in your dependencies?
O3 Security finds GHSA-9v3m-8fp8-mj99 across Maven, npm, NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.