Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-jfp7-79g7-89rf

TYPO3 CMS vulnerable to Weak Authentication in Frontend Login

CVSS 5.9 MediumEPSS 0.0051 · 43rd percentile

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

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist<8.7.49 || >=9.0.0, <9.5.38 || >=10.0.0, <10.4.33 || >=11.0.0, <11.5.20 || >=12.0.0, <12.1.18.7.49, 9.5.38, 10.4.33, 11.5.20, 12.1.1
typo3/cmsPackagist>=10.0.0, <10.4.33 || >=11.0.0, <11.5.20 || >=12.0.0, <12.1.110.4.33, 11.5.20, 12.1.1
Identifiers
GHSA-jfp7-79g7-89rf · BIT-typo3-2022-23501 · CVE-2022-23501 · PKSA-hf6f-qcwd-7279 · PKSA-sy8t-czj6-2rjr
Weakness (CWE)
CWE-287 · CWE-302
Tags
Published
13 Dec 2022
Updated
6 Dec 2023

Machine-written summary

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

TYPO3 CMS (packages typo3/cms-core and typo3/cms) has a weakness in frontend login where restricting logins to users in specific storage folders can be bypassed through ambiguous usernames. An attacker who already knows valid credentials could use this to access a different account. Upgrade typo3/cms-core to 8.7.49, 9.5.38, 10.4.33, 11.5.20 or 12.1.1 as appropriate for your branch, or typo3/cms to 10.4.33, 11.5.20 or 12.1.1.

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.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0051, the 43rd percentile, on 5 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.