CVE-2021-3271 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in pressbooks/pressbooks. 2 public exploit references exist, so weaponization risk is real. A fix is available for pressbooks/pressbooks — see the affected versions and patch details below.
Stored cross-site scripting in PressBooks
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-3271 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
pressbooks/pressbooksReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
PressBooks 5.17.3 contains a cross-site scripting (XSS). Stored XSS can be submitted via the Book Info's Long Description Body, and all actions to open or preview the books page will result in the triggering the stored XSS.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | pressbooks/pressbooks | all versions | 5.18.0composer require pressbooks/pressbooks:^5.18.0 |
Affected Products
pressbookspressbooksResearch 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 pressbooks/pressbooks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pressbooks/pressbooks to 5.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3271 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-2021-3271 in your dependencies?
Find it across Packagist, including transitive dependencies.