contao/comments-bundle vulnerabilities
Adds comments functionality to Contao
- Registry
- Composer
- Latest
- 6.0.6
- License
- LGPL-3.0-or-later
2 known advisories
The latest version, 6.0.6, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require contao/comments-bundle:^6.0.6Is 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
Security advisories for contao/comments-bundle
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
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
Is your contao/comments-bundle version vulnerable?
- contao/comments-bundle 6.0No known advisories in 6.0.6
- contao/comments-bundle 5.7No known advisories in 5.7.17
- contao/comments-bundle 5.61 advisory in 5.6.11
- contao/comments-bundle 5.51 advisory in 5.5.16
- contao/comments-bundle 5.41 advisory in 5.4.14
- contao/comments-bundle 5.3No known advisories in 5.3.54
- contao/comments-bundle 5.22 advisories in 5.2.10
- contao/comments-bundle 4.131 advisory in 4.13.58
- contao/comments-bundle 4.122 advisories in 4.12.7
- contao/comments-bundle 4.112 advisories in 4.11.9
- contao/comments-bundle 4.102 advisories in 4.10.7
- contao/comments-bundle 4.92 advisories in 4.9.42
- contao/comments-bundle 4.82 advisories in 4.8.8
Which of your client projects still run an old contao/comments-bundle?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.