GHSA-jpp7-7chh-cf67 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in parse-url. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for parse-url — 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.
parse-urlnpmDescription
Cross-site Scripting (XSS) - Stored in GitHub repository ionicabizau/parse-url prior to 7.0.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | parse-url | all versions | 6.0.1npm install parse-url@6.0.1 |
Affected Products
parse-urlparse-url_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 parse-url, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-url to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jpp7-7chh-cf67 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-jpp7-7chh-cf67 in your dependencies?
Find it across npm, including transitive dependencies.