Is typo3/cms-core 13.2 vulnerable?
Composer · 2 releases from 13.2.0 to 13.2.1 · latest typo3/cms-core is 14.3.10 · checked 2 Nov 2026
Yes: 21 known advisories
Yes. typo3/cms-core 13.2.1, the last 13.2 release, is affected by 21 known security advisories (5 high, 13 medium, 3 low), including CVE-2026-11607, CVE-2026-47343, CVE-2026-47346. Upgrade to 13.4.31 or later to fix all of them.
composer require typo3/cms-core:^13.4.31Advisories affecting typo3/cms-core 13.2.1
TYPO3 CMS has Broken Access Control in its Form Framework
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Broken Access Control in the Recycler Module
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has an Open Redirect Vulnerability via Core Utilities
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS: Destructive Actions on File Mount Folders
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Broken Access Control in its DataHandler
- Affected
- >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 13.4.31, 14.3.3
TYPO3 CMS has Broken Access Control in its Form Framework
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Broken Access Control in its Media Module
- Affected
- >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Insecure Deserialization via Core API
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Broken Access Control in its File Abstraction Layer
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Broken Access Control in Backend API
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS: Broken Access Control in Media Module
- Affected
- <10.4.57 · >=11.0.0 <11.5.51 · >=12.0.0 <12.4.46 · >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
TYPO3 CMS has Cross-Site Scripting in Indexed Search
- Affected
- >=13.0.0 <13.4.31 · >=14.0.0 <14.3.3
- Fixed in
- 13.4.31, 14.3.3
TYPO3 CMS Allows Insecure Deserialization via Mailer File Spool
- Affected
- >=14.0.0 <14.0.2 · >=13.0.0 <13.4.23 · >=12.0.0 <12.4.41 · >=11.0.0 <11.5.49 · >=10.0.0 <10.4.55
- Fixed in
- 10.4.55, 11.5.49, 12.4.41, 13.4.23, 14.0.2
TYPO3 CMS exposes sensitive information in an error message
- Affected
- >=9.0.0 <12.4.37 · >=10.0.0 <12.4.37 · >=11.0.0 <12.4.37 · >=12.0.0 <12.4.37 · >=13.0.0 <13.4.18
- Fixed in
- 12.4.37, 13.4.18
TYPO3 CMS has an open‑redirect vulnerability
- Affected
- >=9.0.0 <12.4.37 · >=10.0.0 <12.4.37 · >=11.0.0 <12.4.37 · >=12.0.0 <12.4.37 · >=13.0.0 <13.4.18
- Fixed in
- 12.4.37, 13.4.18
TYPO3 CMS uses insufficient entropy when generating passwords
- Affected
- >=12.0.0 <12.4.37 · >=13.0.0 <13.4.18
- Fixed in
- 12.4.37, 13.4.18
TYPO3 Allows Privilege Escalation to System Maintainer
- Affected
- >=10.4.0 <10.4.50 · >=11.0.0 <11.5.44 · >=12.0.0 <12.4.31 · >=13.0.0 <13.4.12
- Fixed in
- 10.4.50, 11.5.44, 12.4.31, 13.4.12
TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
- Affected
- >=9.0.0 <9.5.51 · >=10.0.0 <10.4.50 · >=11.0.0 <11.5.44 · >=12.0.0 <12.4.31 · >=13.0.0 <13.4.12
- Fixed in
- 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12
TYPO3 Unverified Password Change for Backend Users
- Affected
- >=9.0.0 <9.5.51 · >=10.0.0 <10.4.50 · >=11.0.0 <11.5.44 · >=12.0.0 <12.4.31 · >=13.0.0 <13.4.12
- Fixed in
- 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12
TYPO3 Allows Information Disclosure via DBAL Restriction Handling
- Affected
- >=9.0.0 <9.5.51 · >=10.0.0 <10.4.50 · >=11.0.0 <11.5.44 · >=12.0.0 <12.4.31 · >=13.0.0 <13.4.12
- Fixed in
- 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12
TYPO3 Potential Open Redirect via Parsing Differences
- Affected
- >=9.0.0 <9.5.49 · >=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
- 9.5.49, 10.4.48, 11.5.42, 12.4.25, 13.4.3
Which of your client projects are still on typo3/cms-core 13.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact typo3/cms-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other typo3/cms-core versions
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.