CVE-2022-23501

Problem

Restricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.

References

• TYPO3-CORE-SA-2022-013

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2022-23501 has a CVSS score of 5.9 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.7.49, 9.5.38, 10.4.33, 11.5.20, 12.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.

1. What is CVE-2022-23501? CVE-2022-23501 is a medium-severity improper authentication vulnerability in typo3/cms-core (composer), affecting versions < 8.7.49. It is fixed in 8.7.49, 9.5.38, 10.4.33, 11.5.20, 12.1.1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2022-23501? CVE-2022-23501 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-23501?
   • typo3/cms-core (composer) (versions < 8.7.49)
   • typo3/cms (composer) (versions >= 10.0.0, < 10.4.33)
4. Is there a fix for CVE-2022-23501? Yes. CVE-2022-23501 is fixed in 8.7.49, 9.5.38, 10.4.33, 11.5.20, 12.1.1. Upgrade to this version or later.
5. Is CVE-2022-23501 exploitable, and should I be worried? Whether CVE-2022-23501 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-23501 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-23501?
   • Upgrade typo3/cms-core to 8.7.49 or later
   • Upgrade typo3/cms-core to 9.5.38 or later
   • Upgrade typo3/cms-core to 10.4.33 or later
   • Upgrade typo3/cms-core to 11.5.20 or later
   • Upgrade typo3/cms-core to 12.1.1 or later
   • Upgrade typo3/cms to 10.4.33 or later
   • Upgrade typo3/cms to 11.5.20 or later
   • Upgrade typo3/cms to 12.1.1 or later