Advisory record · GHSA-m392-235j-9r7r

TYPO3 CMS vulnerable to User Enumeration via Response Timing

CVSS 5.3 MediumEPSS 0.013 · 70th percentile

Published by the GitHub Advisory Database at 16 Sept 2022, 17:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist>=7.0.0, <7.6.58 || >=8.0.0, <8.7.48 || >=9.0.0, <9.5.37 || >=10.0.0, <10.4.32 || >=11.0.0, <11.5.167.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16
typo3/cmsPackagist>=10.0.0, <10.4.32 || >=11.0.0, <11.5.1610.4.32, 11.5.16
Identifiers
GHSA-m392-235j-9r7r · BIT-typo3-2022-36105 · CVE-2022-36105 · PKSA-d4cy-7k8v-3wtm · PKSA-rrh7-bw6s-dw97
Weakness (CWE)
CWE-203
Published
16 Sept 2022
Updated
6 Dec 2023

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

TYPO3 CMS core (typo3/cms-core, versions 7.0.0 up to but not including 7.6.58, 8.0.0 to before 8.7.48, 9.0.0 to before 9.5.37, 10.0.0 to before 10.4.32, and 11.0.0 to before 11.5.16) and typo3/cms are affected by a user enumeration flaw in which response timing during backend and frontend login reveals whether an account exists. An attacker who can reach the login forms over the network can use timing differences to identify valid usernames. Upgrade typo3/cms-core to 7.6.58, 8.7.48, 9.5.37, 10.4.32 or 11.5.16, and typo3/cms to 10.4.32 or 11.5.16.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.013, the 70th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:32 UTC First seen by agentprime
  2. 31 Oct 2026, 14:32 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.