TYPO3 CMS has an Open Redirect Vulnerability via Core Utilities
Published 12 Jun 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- <10.4.57
- Fixed in
- 10.4.57
composer require typo3/cms-core:^10.4.57- Affected
- >=11.0.0 <11.5.51
- Fixed in
- 11.5.51
composer require typo3/cms-core:^11.5.51- Affected
- >=12.0.0 <12.4.46
- Fixed in
- 12.4.46
composer require typo3/cms-core:^12.4.46- Affected
- >=13.0.0 <13.4.31
- Fixed in
- 13.4.31
composer require typo3/cms-core:^13.4.31- Affected
- >=14.0.0 <14.3.3
- Fixed in
- 14.3.3
composer require typo3/cms-core:^14.3.3Details
Problem
Applications that use GeneralUtility::sanitizeLocalUrl to allow only local URLs are vulnerable to open redirect attacks if the URL is used after it has passed the aforementioned sanitization checks. This enables attackers to redirect users to external content and carry out phishing attacks.
Solution
Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.
Credits
TYPO3 CMS thanks Alexandre Romao for reporting this issue, and TYPO3 core & security team member Benjamin Franzke for fixing it.
Resources
Is GHSA-3p42-w5ch-gg42 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-3p42-w5ch-gg42
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-47347
- Linkgithub.com/TYPO3/typo3/commit/22c2dd5398ebc4cb7aa4aa37e02cb39181dee0cd
- Linkgithub.com/TYPO3/typo3/commit/3ffc0835012c6199db0e1dc4b56a77147d8600e0
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-47347.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2026-009
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.