CVE-2024-47780

Information Disclosure in TYPO3 Page Tree

Problem

Backend users could see items in the backend page tree without having access if the mounts pointed to pages restricted for their user/group, or if no mounts were configured but the pages allowed access to "everybody." However, affected users could not manipulate these pages.

Credits

Thanks to Peter Schuler who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.

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-2024-47780 has a CVSS score of 3.1 (Low). 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 (13.3.1, 12.4.21, 11.5.40, 10.4.46); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Update to TYPO3 versions 10.4.46 ELTS, 11.5.40 LTS, 12.4.21 LTS, 13.3.1 that fix the problem described.

1. What is CVE-2024-47780? CVE-2024-47780 is a low-severity incorrect authorization vulnerability in typo3/cms-backend (composer), affecting versions >= 13.0.0, < 13.3.1. It is fixed in 13.3.1, 12.4.21, 11.5.40, 10.4.46. 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-2024-47780? CVE-2024-47780 has a CVSS score of 3.1 (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-backend are affected by CVE-2024-47780? typo3/cms-backend (composer) versions >= 13.0.0, < 13.3.1 is affected.
4. Is there a fix for CVE-2024-47780? Yes. CVE-2024-47780 is fixed in 13.3.1, 12.4.21, 11.5.40, 10.4.46. Upgrade to this version or later.
5. Is CVE-2024-47780 exploitable, and should I be worried? Whether CVE-2024-47780 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-2024-47780 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-2024-47780?
   • Upgrade typo3/cms-backend to 13.3.1 or later
   • Upgrade typo3/cms-backend to 12.4.21 or later
   • Upgrade typo3/cms-backend to 11.5.40 or later
   • Upgrade typo3/cms-backend to 10.4.46 or later

Other vulnerabilities in typo3/cms-backend