GHSA-98f7-p5rc-jx67 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in materialize-css. 1 public exploit reference exists, so weaponization risk is real. A fix is available for materialize-css — see the affected versions and patch details below.
Materialize-css vulnerable to Cross-site Scripting in tooltip component
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-98f7-p5rc-jx67 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,333 CVEs with a current EPSS score, this one falls in the < 10% 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.
materialize-cssnpm@materializecss/materializenpmDescription
All versions of materialize-css are vulnerable to Cross-Site Scripting. The tooltip component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user.
Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | materialize-css | all versions | No fix |
| 📦npm | @materializecss/materialize | all versions | 1.1.0-alphanpm install @materializecss/materialize@1.1.0-alpha |
Research 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 materialize-css, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of materialize-css has shipped for GHSA-98f7-p5rc-jx67 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-98f7-p5rc-jx67 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-98f7-p5rc-jx67. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-98f7-p5rc-jx67 in your dependencies?
O3 Security finds GHSA-98f7-p5rc-jx67 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.