CVE-2026-47352: TYPO3 CMS - Broken Access Control in Backend API

Published Jun 9, 2026
·
Updated

Problem Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outside their permitted file mounts or storages.

Solution Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits TYPO3 CMS thanks Phong Lan for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.

Resources TYPO3-CORE-SA-2026-015

Other sources

Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outside their permitted file mounts or storages. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.

— MITRE

Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outside their permitted file mounts or storages. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, 13.0.0-13.4.31 and 14.0.0-14.3.3.

— NVD

Affected Software

11 affected componentsFixes available
Typo3 TYPO3 CMS<10.4.57, >=11.0.0<=11.5.51, >=12.0.0<=12.4.46, >=13.0.0<=13.4.31, >=14.0.0<=14.3.3
composer/typo3/cms-backend>=14.0.0<14.3.3
14.3.3
composer/typo3/cms-backend>=13.0.0<13.4.31
13.4.31
composer/typo3/cms-backend>=12.0.0<12.4.46
12.4.46
composer/typo3/cms-backend>=11.0.0<11.5.51
11.5.51
composer/typo3/cms-backend<10.4.57
10.4.57
composer/typo3/cms-core>=14.0.0<14.3.3
14.3.3
composer/typo3/cms-core>=13.0.0<13.4.31
13.4.31
composer/typo3/cms-core>=12.0.0<12.4.46
12.4.46
composer/typo3/cms-core>=11.0.0<11.5.51
11.5.51
composer/typo3/cms-core<10.4.57
10.4.57

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 14.3.3
  2. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 13.4.31
  3. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 12.4.46
  4. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 11.5.51
  5. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 10.4.57
  6. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 14.3.3
  7. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 13.4.31
  8. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 12.4.46
  9. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 11.5.51
  10. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 10.4.57
  11. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 10.4.57 ELTS
  12. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 11.5.51 ELTS
  13. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 12.4.46 ELTS
  14. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 13.4.31 LTS
  15. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 14.3.3 LTS
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch TYPO3-CORE-SA-2026-015

Event History

Jun 9, 2026
CVE Published
via MITRE·10:53 AM
Data Sourced
via MITRE·10:53 AM
DescriptionWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Jun 12, 2026
Advisory Published
via GitHub·07:08 PM
Data Sourced
via GitHub·07:08 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-47352?

CVE-2026-47352 has a medium severity rating of 5.3 according to the CVSS scoring system.

2

How do I fix CVE-2026-47352?

To fix CVE-2026-47352, update TYPO3 CMS to versions 10.4.57, 11.5.51, 12.4.46, or later.

3

What is the impact of CVE-2026-47352?

CVE-2026-47352 allows authenticated backend users to access file metadata without proper permission checks, potentially exposing unauthorized files.

4

Which TYPO3 versions are affected by CVE-2026-47352?

CVE-2026-47352 affects TYPO3 CMS versions prior to 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, and 13.0.0-13.4.

5

Who is at risk with CVE-2026-47352?

Authenticated users with backend access in TYPO3 CMS are at risk from CVE-2026-47352 due to inadequate access control.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203