TYPO3 CMS has Broken Access Control in Backend API

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-47352: 0.24% estimated exploitation activity in the next 30 days; percentile 14.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

12 Jun 2026, 19:08 UTC

Last modified by the source

12 Jun 2026, 19:09 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2j54-93q2-3hjq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47352

Advisory: TYPO3 CMS has Broken Access Control in Backend API
IDs: CVE-2026-47352, GHSA-2j54-93q2-3hjq
Record: https://patchnext.com/advisories/cve-2026-47352 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-backend 14.3.3, 13.4.31, 12.4.46, 11.5.51, 10.4.57; typo3/cms-core 14.3.3, 13.4.31, 12.4.46, 11.5.51, 10.4.57. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-backend: affected < 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; fixed in 11.5.51, 13.4.31, 10.4.57, 12.4.46, 14.3.3
- Packagist typo3/cms-core: affected < 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; fixed in 11.5.51, 13.4.31, 10.4.57, 12.4.46, 14.3.3

## Suggested inspection (read-only)
- Packagist typo3/cms-backend: check the installed version with your package manager.
- Packagist typo3/cms-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-backend, typo3/cms-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2j54-93q2-3hjq (GitHub-reviewed advisory GHSA-2j54-93q2-3hjq lists affected ranges: Packagist typo3/cms-core >=0 =11.0.0 =12.0.0 =13.0.0 =14.0.0 =0 =11.0.0 =12.0.0 =13.0.0 =14.0.0 <14.3.3)

Commands are suggestions: review each one before running it.