CVE-2017-1000006 — plotly.js
MEDIUMCVE-2017-1000006 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in plotly.js. A fix is available for plotly.js — see the affected versions and patch details below.
Cross Site Scripting (XSS) in plotly.js
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.
plotly.jsnpmDescription
Affected versions of plotly.js are vulnerable to cross-site scripting if an attacker can convince a user to visit a malicious plot on a site using this package.
Recommendation
Update to 1.16.0 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | plotly.js | all versions | 1.16.0npm install plotly.js@1.16.0 |
Affected Products
plotly.jsplotlyDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plotly.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update plotly.js to 1.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000006 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-1000006 in your dependencies?
Find it across npm, including transitive dependencies.