---
id: CVE-2026-47352
aliases:
  - GHSA-2j54-93q2-3hjq
title: TYPO3 CMS has Broken Access Control in Backend API
summary: TYPO3 CMS has Broken Access Control in Backend API
severity: medium
cwe:
  - CWE-862
vendor: typo3
product: typo3/cms-core
ecosystem: composer
affected:
  - typo3/cms-core < 10.4.57
  - 'typo3/cms-core >= 11.0.0, < 11.5.51'
  - 'typo3/cms-core >= 12.0.0, < 12.4.46'
  - 'typo3/cms-core >= 13.0.0, < 13.4.31'
  - 'typo3/cms-core >= 14.0.0, < 14.3.3'
  - typo3/cms-backend < 10.4.57
  - 'typo3/cms-backend >= 11.0.0, < 11.5.51'
  - 'typo3/cms-backend >= 12.0.0, < 12.4.46'
  - 'typo3/cms-backend >= 13.0.0, < 13.4.31'
  - 'typo3/cms-backend >= 14.0.0, < 14.3.3'
patched:
  - typo3/cms-core 10.4.57
  - typo3/cms-core 11.5.51
  - typo3/cms-core 12.4.46
  - typo3/cms-core 13.4.31
  - typo3/cms-core 14.3.3
  - typo3/cms-backend 10.4.57
  - typo3/cms-backend 11.5.51
  - typo3/cms-backend 12.4.46
  - typo3/cms-backend 13.4.31
  - typo3/cms-backend 14.3.3
published: '2026-06-12'
updated: '2026-06-12'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-2j54-93q2-3hjq'
references:
  - url: 'https://github.com/TYPO3/typo3/security/advisories/GHSA-2j54-93q2-3hjq'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-47352'
  - url: >-
      https://github.com/TYPO3/typo3/commit/17a3b7830d5931725db5fdab0cfc76d479884c96
  - url: >-
      https://github.com/TYPO3/typo3/commit/bfe7c354168f467726020ed49299dd209a455719
  - url: >-
      https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-47352.yaml
  - url: 'https://typo3.org/security/advisory/typo3-core-sa-2026-015'
  - url: 'https://github.com/advisories/GHSA-2j54-93q2-3hjq'
tags:
  - ghsa
  - composer
epss: 0.00238
epssPercentile: 0.15117
ingestedAt: '2026-07-07T15:41:59.193Z'
---

## Overview

### 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](https://typo3.org/security/advisory/typo3-core-sa-2026-015)

## Affected packages

- `typo3/cms-core < 10.4.57`
- `typo3/cms-core >= 11.0.0, < 11.5.51`
- `typo3/cms-core >= 12.0.0, < 12.4.46`
- `typo3/cms-core >= 13.0.0, < 13.4.31`
- `typo3/cms-core >= 14.0.0, < 14.3.3`
- `typo3/cms-backend < 10.4.57`
- `typo3/cms-backend >= 11.0.0, < 11.5.51`
- `typo3/cms-backend >= 12.0.0, < 12.4.46`
- `typo3/cms-backend >= 13.0.0, < 13.4.31`
- `typo3/cms-backend >= 14.0.0, < 14.3.3`

## Remediation

Upgrade to a patched release:

- `typo3/cms-core 10.4.57`
- `typo3/cms-core 11.5.51`
- `typo3/cms-core 12.4.46`
- `typo3/cms-core 13.4.31`
- `typo3/cms-core 14.3.3`
- `typo3/cms-backend 10.4.57`
- `typo3/cms-backend 11.5.51`
- `typo3/cms-backend 12.4.46`
- `typo3/cms-backend 13.4.31`
- `typo3/cms-backend 14.3.3`