GHSA-RXC9-F2X6-QH4W

When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However, this leads to persisting the current state as well, which can result into some of the following:

• account contains empty login credentials (username and/or password)
• account is incomplete and contains weak credentials (username and/or password)

Albeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations.

This weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.

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.

GHSA-RXC9-F2X6-QH4W has a CVSS score of 7.5 (High). The vector is network-reachable, no 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.23, 9.5.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-RXC9-F2X6-QH4W? GHSA-RXC9-F2X6-QH4W is a high-severity improper authentication vulnerability in typo3/cms-core (composer), affecting versions >= 8.0.0, < 8.7.23. It is fixed in 8.7.23, 9.5.4. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is GHSA-RXC9-F2X6-QH4W? GHSA-RXC9-F2X6-QH4W has a CVSS score of 7.5 (High). 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 GHSA-RXC9-F2X6-QH4W? typo3/cms-core (composer) versions >= 8.0.0, < 8.7.23 is affected.
4. Is there a fix for GHSA-RXC9-F2X6-QH4W? Yes. GHSA-RXC9-F2X6-QH4W is fixed in 8.7.23, 9.5.4. Upgrade to this version or later.
5. Is GHSA-RXC9-F2X6-QH4W exploitable, and should I be worried? Whether GHSA-RXC9-F2X6-QH4W 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 GHSA-RXC9-F2X6-QH4W 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 GHSA-RXC9-F2X6-QH4W?
   • Upgrade typo3/cms-core to 8.7.23 or later
   • Upgrade typo3/cms-core to 9.5.4 or later

Other vulnerabilities in typo3/cms-core