MediumGHSA-4jhw-2p6j-5wmpBIT-typo3-2021-21338CVE-2021-21338

Open Redirection in Login Handling

Published 23 Mar 2021 · Updated 8 Jul 2026

Affected packages

Affected
>=6.2.0 <6.2.57
Fixed in
6.2.57
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^6.2.57
Affected
>=7.0.0 <7.6.51
Fixed in
7.6.51
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^7.6.51
Affected
>=8.0.0 <8.7.40
Fixed in
8.7.40
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.40
Affected
>=10.0.0 <10.4.14
Fixed in
10.4.14
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.14
Affected
>=11.0.0 <11.1.1
Fixed in
11.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.1.1
Affected
>=9.0.0 <9.5.25
Fixed in
9.5.25
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.25
typo3/cmsComposer
Affected
>=10.0.0 <10.4.14
Fixed in
10.4.14
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.14
typo3/cmsComposer
Affected
>=11.0.0 <11.1.1
Fixed in
11.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.1.1
typo3/cmsComposer
Affected
>=9.0.0 <9.5.25
Fixed in
9.5.25
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.25

Details

Problem

It has been discovered that Login Handling is susceptible to open redirection which allows attackers redirecting to arbitrary content, and conducting phishing attacks. No authentication is required in order to exploit this vulnerability.

Solution

Update to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.

Credits

Thanks to Alexander Kellner who reported this issue and to TYPO3 security team member Torben Hansen who fixed the issue.

References

Is GHSA-4jhw-2p6j-5wmp 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

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.