HighGHSA-954j-f27r-cj52BIT-typo3-2020-26228CVE-2020-26228

Cleartext storage of session identifier

Published 23 Nov 2020 · Updated 8 Jul 2026

Affected packages

typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.23
Fixed in
9.5.23
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.23
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.10
Fixed in
10.4.10
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.10
typo3/cms-coreComposer
Affected
>=8.7.0 <8.7.38
Fixed in
8.7.38
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.38
typo3/cmsComposer
Affected
>=10.0.0 <10.4.10
Fixed in
10.4.10
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.10
typo3/cmsComposer
Affected
>=9.0.0 <9.5.23
Fixed in
9.5.23
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.23
typo3/cmsComposer
Affected
>=8.7.0 <8.7.38
Fixed in
8.7.38
Update to the fixed version for your release line, for example:composer require typo3/cms:^8.7.38

Details

User session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.

Solution

Update to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.

Credits

Thanks to TYPO3 security team member Helmut Hummel who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader as well as TYPO3 contributor Markus Klein who fixed the issue.

Is GHSA-954j-f27r-cj52 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.

Scan a project free, no signupOr connect GitHub to scan every repo

References

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