CVE-2025-47937

Problem

When performing a database query involving multiple tables through the database abstraction layer (DBAL), frontend user permissions are only applied via FrontendGroupRestriction to the last table. As a result, data from additional tables included in the same query may be unintentionally exposed to unauthorized users.

Credits

Thanks to Christian Futterlieb for reporting this issue, and to TYPO3 security team member Elias Häußler for fixing it.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2025-47937 has a CVSS score of 3.7 (Low). 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 (9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.

1. What is CVE-2025-47937? CVE-2025-47937 is a low-severity incorrect authorization vulnerability in typo3/cms-core (composer), affecting versions >= 9.0.0, <= 9.5.50. It is fixed in 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2025-47937? CVE-2025-47937 has a CVSS score of 3.7 (Low). 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-2025-47937? typo3/cms-core (composer) versions >= 9.0.0, <= 9.5.50 is affected.
4. Is there a fix for CVE-2025-47937? Yes. CVE-2025-47937 is fixed in 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12. Upgrade to this version or later.
5. Is CVE-2025-47937 exploitable, and should I be worried? Whether CVE-2025-47937 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-2025-47937 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-2025-47937?
   • Upgrade typo3/cms-core to 9.5.51 or later
   • Upgrade typo3/cms-core to 10.4.50 or later
   • Upgrade typo3/cms-core to 11.5.44 or later
   • Upgrade typo3/cms-core to 12.4.31 or later
   • Upgrade typo3/cms-core to 13.4.12 or later