All reports
Medium

TYPO3 CMS vulnerable to User Enumeration via Response Timing

Affected versions

Version ranges need review.

Affected versions
>= 9.0.0, < 9.5.37
Fixed version
9.5.37
Affected versions
>=10.0.0,<10.4.32|>=11.0.0,<11.5.16
Fixed version
Not reported
Affected versions
>= 10.0.0, < 10.4.32
Fixed version
10.4.32
Affected versions
>= 8.0.0, < 8.7.48
Fixed version
8.7.48
Affected versions
>= 11.0.0, < 11.5.16
Fixed version
11.5.16
Affected versions
>= 7.0.0, < 7.6.58
Fixed version
7.6.58
Composertypo3/cms
Affected versions
>= 11.0.0, < 11.5.16
Fixed version
11.5.16
Composertypo3/cms
Affected versions
>=10.0.0,<10.4.32|>=11.0.0,<11.5.16
Fixed version
Not reported
Composertypo3/cms
Affected versions
>= 10.0.0, < 10.4.32
Fixed version
10.4.32

Exploitation

CVE-2022-36105

Probability of exploitation in the next 30 days: 1.29%

FIRST EPSS · 2026-11-21

Description

Meta
  • CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C (4.9)

Problem

It has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts.

Extension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new MimicServiceInterface::mimicAuthUser, which simulates corresponding times regular processing would usually take.

Solution

Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.

Credits

Thanks to Vautia who reported this issue and to TYPO3 core & security team members Oliver Hader who fixed the issue.

References

Links

Credits

  • Vautia