CVE-2022-36105: TYPO3 CMS vulnerable to User Enumeration via Response Timing

medium Affects typo3/cms, typo3/cms-core. Feed 2026.10.29.3, updated 2026-10-29; published ; advisory modified .

TYPO3 CMS vulnerable to User Enumeration via Response Timing

Package
typo3/cms Composer
Affected versions
>=10.0.0 and <10.4.32 or >=11.0.0 and <11.5.16
Fixed in
10.4.32, 11.5.16
Severity
medium  CVSS 5.3
Exploitation
not on CISA KEV · EPSS 1% (69.6th percentile)
Published
2022-09-16
Source
osv.dev

References

TYPO3 CMS vulnerable to User Enumeration via Response Timing

Package
typo3/cms-core Composer
Affected versions
>=7.0.0 and <7.6.58 or >=8.0.0 and <8.7.48 or >=9.0.0 and <9.5.37 or >=10.0.0 and <10.4.32 or >=11.0.0 and <11.5.16
Fixed in
7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16
Severity
medium  CVSS 5.3
Exploitation
not on CISA KEV · EPSS 1% (69.6th percentile)
Published
2022-09-16
Source
osv.dev

References

CWE-203
NVD recordtypo3/cms advisoriestypo3/cms-core advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked

Related advisories