CVE-2017-0931 — html-janitor
MEDIUMCVE-2017-0931 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in html-janitor. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for html-janitor — see the affected versions and patch details below.
Cross-Site Scripting in html-janitor
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.
html-janitornpmDescription
Versions of html-janitor prior to 2.0.2 (all current versions) are vulnerable to cross-site scripting (XSS).
This is exploitable if user-controlled data is passed into the modules clean() function.
Recommendation
No fix is currently available for this vulnerability. It is recommended to use an alternative module for HTML sanitization.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | html-janitor | all versions | 2.0.3npm install html-janitor@2.0.3 |
Affected Products
html-janitorhtml-janitor_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 html-janitor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update html-janitor to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-0931 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 CVE-2017-0931 in your dependencies?
Find it across npm, including transitive dependencies.