CVE-2020-8127 — reveal.js
MEDIUMCVE-2020-8127 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in reveal.js. 1 public exploit reference exists, so weaponization risk is real. A fix is available for reveal.js — see the affected versions and patch details below.
Cross-site Scripting in reveal.js
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-8127 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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.
reveal.jsnpmDescription
Insufficient validation in cross-origin communication (postMessage) in reveal.js version 3.9.1 and earlier allow attackers to perform cross-site scripting attacks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | reveal.js | all versions | 3.9.2npm install reveal.js@3.9.2 |
Affected Products
reveal.jsrevealjsResearch 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 reveal.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update reveal.js to 3.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-8127 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-2020-8127 in your dependencies?
Find it across npm, including transitive dependencies.