CVE-2021-21365 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in bk2k/bootstrap-package. 2 public exploit references exist, so weaponization risk is real. A fix is available for bk2k/bootstrap-package — see the affected versions and patch details below.
Cross-Site Scripting in Bootstrap Package
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-21365 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
bk2k/bootstrap-package🐘bk2k/bootstrap-package🐘bk2k/bootstrap-package🐘bk2k/bootstrap-package🐘bk2k/bootstrap-package🐘bk2k/bootstrap-packageReal-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
Problem
It has been discovered that rendering content in the website frontend is vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.
The following templates are affected by the vulnerability:
Resources/Private/Partials/ContentElements/Carousel/Item/CallToAction.htmlResources/Private/Partials/ContentElements/Carousel/Item/Header.htmlResources/Private/Partials/ContentElements/Carousel/Item/Text.htmlResources/Private/Partials/ContentElements/Carousel/Item/TextAndImage.htmlResources/Private/Partials/ContentElements/Header/SubHeader.html
Users of the extension, who have overwritten the affected templates with custom code must manually apply the security fix as shown in this Git commit.
Solution
Update to version 7.1.2, 8.0.8, 9.0.4, 9.1.3, 10.0.10 or 11.0.3 of the Bootstrap Package that fix the problem described.
Updated version are available from the TYPO3 extension manager, Packagist and at https://extensions.typo3.org/extension/download/bootstrap_package/.
Credits
Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | bk2k/bootstrap-package | ≥ 7.1.0&&< 7.1.2 | 7.1.2composer require bk2k/bootstrap-package:^7.1.2 |
| 🐘Packagist | bk2k/bootstrap-package | ≥ 8.0.0&&< 8.0.8 | 8.0.8composer require bk2k/bootstrap-package:^8.0.8 |
| 🐘Packagist | bk2k/bootstrap-package | ≥ 9.0.0&&< 9.0.4 | 9.0.4composer require bk2k/bootstrap-package:^9.0.4 |
| 🐘Packagist | bk2k/bootstrap-package | ≥ 9.1.0&&< 9.1.3 | 9.1.3composer require bk2k/bootstrap-package:^9.1.3 |
| 🐘Packagist | bk2k/bootstrap-package | ≥ 10.0.0&&< 10.0.10 | 10.0.10composer require bk2k/bootstrap-package:^10.0.10 |
| 🐘Packagist | bk2k/bootstrap-package | ≥ 11.0.0&&< 11.0.3 | 11.0.3composer require bk2k/bootstrap-package:^11.0.3 |
Affected Products
typo3typo3Research 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 bk2k/bootstrap-package, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bk2k/bootstrap-package to 7.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21365 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-21365 in your dependencies?
Find it across Packagist, including transitive dependencies.