MediumGHSA-34fr-fhqr-7235BIT-typo3-2021-32767CVE-2021-32767

Information Disclosure in User Authentication

Published 26 Jul 2021 · Updated 8 Jul 2026

Affected packages

typo3/cms-coreComposer
Affected
>=7.0.0 <7.6.52
Fixed in
7.6.52
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^7.6.52
typo3/cms-coreComposer
Affected
>=8.0.0 <8.7.41
Fixed in
8.7.41
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.41
typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.28
Fixed in
9.5.28
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.28
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.18
Fixed in
10.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.18
typo3/cms-coreComposer
Affected
>=11.0.0 <11.3.1
Fixed in
11.3.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.3.1
typo3/cmsComposer
Affected
>=10.0.0 <10.4.18
Fixed in
10.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.18
typo3/cmsComposer
Affected
>=11.0.0 <11.3.1
Fixed in
11.3.1
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.3.1
typo3/cmsComposer
Affected
>=9.0.0 <9.5.28
Fixed in
9.5.28
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.28

Details

> ### Meta > * CVSS: AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C (4.9)

Problem

It has been discovered that user credentials have been logged as plaintext when explicitly using log level debug, which is not the _default_ configuration.

Solution

Update to TYPO3 versions 7.6.52 ELTS, 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.

Credits

Thanks to Ingo Schmitt who reported this issue, and to TYPO3 core & security team member Benni Mack who fixed the issue.

References

Is GHSA-34fr-fhqr-7235 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.