CVE-2023-47127

CVSS: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N/E:X/RL:O/RC:C (4.0)

Problem

Given that there are at least two different sites in the same TYPO3 installation - for instance first.example.org and second.example.com - then a session cookie generated for the first site can be reused on the second site without requiring additional authentication.

This vulnerability primarily affects the frontend of the website. It's important to note that exploiting this vulnerability requires a valid user account.

Credits

Thanks to Rémy Daniel who reported this issue, and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

• TYPO3-CORE-SA-2023-006

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-2023-47127 has a CVSS score of 4.2 (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.55, 9.5.44, 10.4.41, 11.5.33, 12.4.8); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 versions 8.7.55 ELTS, 9.5.44 ELTS, 10.4.41 ELTS, 11.5.33, 12.4.8 that fix the problem described above.

1. What is CVE-2023-47127? CVE-2023-47127 is a medium-severity improper authentication vulnerability in typo3/cms-core (composer), affecting versions >= 8.0.0, <= 8.7.54. It is fixed in 8.7.55, 9.5.44, 10.4.41, 11.5.33, 12.4.8. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2023-47127? CVE-2023-47127 has a CVSS score of 4.2 (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 versions of typo3/cms-core are affected by CVE-2023-47127? typo3/cms-core (composer) versions >= 8.0.0, <= 8.7.54 is affected.
4. Is there a fix for CVE-2023-47127? Yes. CVE-2023-47127 is fixed in 8.7.55, 9.5.44, 10.4.41, 11.5.33, 12.4.8. Upgrade to this version or later.
5. Is CVE-2023-47127 exploitable, and should I be worried? Whether CVE-2023-47127 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-2023-47127 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-2023-47127?
   • Upgrade typo3/cms-core to 8.7.55 or later
   • Upgrade typo3/cms-core to 9.5.44 or later
   • Upgrade typo3/cms-core to 10.4.41 or later
   • Upgrade typo3/cms-core to 11.5.33 or later
   • Upgrade typo3/cms-core to 12.4.8 or later