typo3/cms-belog vulnerabilities
TYPO3 CMS Log - View logs from the sys_log table in the TYPO3 backend modules System>Log
- Registry
- Composer
- Latest
- 14.3.12
- License
- GPL-2.0-or-later
1 known advisory
The latest version, 14.3.12, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require typo3/cms-belog:^14.3.12Is your project on an affected typo3/cms-belog?
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 typo3/cms-belog
TYPO3 Cross-Site Request Forgery in Log Module
- Affected
- >=10.0.0 <10.4.48 · >=11.0.0 <11.5.42 · >=12.0.0 <12.4.25 · >=13.0.0 <13.4.3
- Fixed in
- 10.4.48, 11.5.42, 12.4.25, 13.4.3
Is your typo3/cms-belog version vulnerable?
- typo3/cms-belog 14.3No known advisories in 14.3.12
- typo3/cms-belog 14.2No known advisories in 14.2.0
- typo3/cms-belog 14.1No known advisories in 14.1.1
- typo3/cms-belog 14.0No known advisories in 14.0.2
- typo3/cms-belog 13.4No known advisories in 13.4.40
- typo3/cms-belog 13.31 advisory in 13.3.1
- typo3/cms-belog 13.21 advisory in 13.2.1
- typo3/cms-belog 13.11 advisory in 13.1.1
- typo3/cms-belog 13.01 advisory in 13.0.1
- typo3/cms-belog 12.4No known advisories in 12.4.45
- typo3/cms-belog 12.31 advisory in 12.3.0
- typo3/cms-belog 12.21 advisory in 12.2.0
- typo3/cms-belog 12.11 advisory in 12.1.3
- typo3/cms-belog 12.01 advisory in 12.0.0
Which of your client projects still run an old typo3/cms-belog?
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.