CVE-2022-0624 is a medium-severity (CVSS 6.5) CWE-639 vulnerability in parse-path. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for parse-path — see the affected versions and patch details below.
Authorization Bypass Through User-Controlled Key in ionicabizau/parse-path
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-pathnpmDescription
Authorization Bypass Through User-Controlled Key in GitHub repository ionicabizau/parse-path prior to 5.0.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | parse-path | all versions | 5.0.0npm install parse-path@5.0.0 |
Affected Products
parse-pathparse-path_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-path, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-path to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0624 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.
Frequently Asked Questions
Is CVE-2022-0624 in your dependencies?
Find it across npm, including transitive dependencies.