typo3/cms-frontend vulnerabilities
TYPO3 CMS Frontend
- Registry
- Composer
- Latest
- 14.3.12
- License
- GPL-2.0-or-later
4 known advisories
The latest version, 14.3.12, is not affected by any of them. Projects on older versions may be.
composer require typo3/cms-frontend:^14.3.12Is your project on an affected typo3/cms-frontend?
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-frontend
TYPO3 Cross-site scripting (XSS) vulnerability in the click enlarge functionality
- Affected
- >=4.3.0 <4.3.9 · >=4.4.0 <4.4.5
- Fixed in
- 4.3.9, 4.4.5
TYPO3 Cross-site scripting (XSS) vulnerability in the FORM content object
- Affected
- >=4.2.0 <4.2.16 · >=4.4.0 <4.4.5 · >=4.3.0 <4.3.9
- Fixed in
- 4.2.16, 4.3.9, 4.4.5
TYPO3 is vulnerable to insecure randomness during hash generation in forgot password function
- Affected
- <4.3.4 · >=4.4.0 <4.4.1
- Fixed in
- 4.3.4, 4.4.1
TYPO3 is vulnerable to Spam Abuse in the native form content element
- Affected
- <4.1.14 · >=4.2.0 <4.2.13 · >=4.3.0 <4.3.4 · >=4.4.0 <4.4.1
- Fixed in
- 4.1.14, 4.2.13, 4.3.4, 4.4.1
Is your typo3/cms-frontend version vulnerable?
- typo3/cms-frontend 14.3No known advisories in 14.3.12
- typo3/cms-frontend 14.2No known advisories in 14.2.0
- typo3/cms-frontend 14.1No known advisories in 14.1.1
- typo3/cms-frontend 14.0No known advisories in 14.0.2
- typo3/cms-frontend 13.4No known advisories in 13.4.40
- typo3/cms-frontend 13.3No known advisories in 13.3.1
- typo3/cms-frontend 13.2No known advisories in 13.2.1
- typo3/cms-frontend 13.1No known advisories in 13.1.1
- typo3/cms-frontend 13.0No known advisories in 13.0.1
- typo3/cms-frontend 12.4No known advisories in 12.4.45
- typo3/cms-frontend 12.3No known advisories in 12.3.0
- typo3/cms-frontend 12.2No known advisories in 12.2.0
- typo3/cms-frontend 12.1No known advisories in 12.1.3
- typo3/cms-frontend 12.0No known advisories in 12.0.0
Which of your client projects still run an old typo3/cms-frontend?
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.