Is contao/comments-bundle 4.13 vulnerable?
Composer · 59 releases from 4.13.0 to 4.13.58 · latest contao/comments-bundle is 6.0.6 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. contao/comments-bundle 4.13.58, the last 4.13 release, is affected by 1 known security advisory (1 critical), including CVE-2026-107845. 1 more affects earlier 4.13.x releases. Upgrade to 5.3.50 or later to fix all of them.
composer require contao/comments-bundle:^5.3.50Is your project on an affected contao/comments-bundle?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting contao/comments-bundle 4.13.58
Contao: Cross-site scripting in the comments bundle
- Affected
- >=4.0.0 <5.3.50 · >=5.4.0-RC1 <5.7.12
- Fixed in
- 5.3.50, 5.7.12
Fixed within 4.13.x, affecting earlier releases
Contao: Insufficient BBCode sanitizer
- Affected
- >=2.0.0 <4.13.40 · >=5.0.0-RC1 <5.3.4
- Fixed in
- 4.13.40, 5.3.4
Every contao/comments-bundle 4.13.x release
Affected: 4.13.0 to 4.13.58. Latest contao/comments-bundle: 6.0.6.
| Version | Known advisories |
|---|---|
| contao/comments-bundle 4.13.58 | CVE-2026-107845 |
| contao/comments-bundle 4.13.57 | CVE-2026-107845 |
| contao/comments-bundle 4.13.56 | CVE-2026-107845 |
| contao/comments-bundle 4.13.55 | CVE-2026-107845 |
| contao/comments-bundle 4.13.54 | CVE-2026-107845 |
| contao/comments-bundle 4.13.53 | CVE-2026-107845 |
| contao/comments-bundle 4.13.52 | CVE-2026-107845 |
| contao/comments-bundle 4.13.51 | CVE-2026-107845 |
| contao/comments-bundle 4.13.50 | CVE-2026-107845 |
| contao/comments-bundle 4.13.49 | CVE-2026-107845 |
| contao/comments-bundle 4.13.48 | CVE-2026-107845 |
| contao/comments-bundle 4.13.47 | CVE-2026-107845 |
| contao/comments-bundle 4.13.46 | CVE-2026-107845 |
| contao/comments-bundle 4.13.45 | CVE-2026-107845 |
| contao/comments-bundle 4.13.44 | CVE-2026-107845 |
| contao/comments-bundle 4.13.43 | CVE-2026-107845 |
| contao/comments-bundle 4.13.42 | CVE-2026-107845 |
| contao/comments-bundle 4.13.41 | CVE-2026-107845 |
| contao/comments-bundle 4.13.40 | CVE-2026-107845 |
| contao/comments-bundle 4.13.39 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.38 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.37 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.36 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.35 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.34 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.33 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.32 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.31 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.30 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.29 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.28 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.27 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.26 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.25 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.24 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.23 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.22 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.21 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.20 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.19 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.18 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.17 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.16 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.15 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.14 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.13 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.12 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.11 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.10 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.9 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.8 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.7 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.6 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.5 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.4 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.3 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.2 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.1 | CVE-2026-107845, CVE-2024-28234 |
| contao/comments-bundle 4.13.0 | CVE-2026-107845, CVE-2024-28234 |
Which of your client projects are still on contao/comments-bundle 4.13?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact contao/comments-bundle version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other contao/comments-bundle versions
- contao/comments-bundle 5.2
- contao/comments-bundle 5.1
- contao/comments-bundle 5.0
- contao/comments-bundle 4.12
- contao/comments-bundle 4.11
- contao/comments-bundle 4.10
- contao/comments-bundle 6.0
- contao/comments-bundle 5.7
- contao/comments-bundle 5.6
- contao/comments-bundle 5.5
- contao/comments-bundle 5.4
- contao/comments-bundle 5.3
- All contao/comments-bundle advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.