---
id: CVE-2026-47351
aliases:
  - GHSA-q93m-25xv-94hh
title: 'TYPO3 CMS: Broken Access Control in Media Module'
summary: 'TYPO3 CMS: Broken Access Control in Media Module'
severity: medium
cwe:
  - CWE-200
  - 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-q93m-25xv-94hh'
references:
  - url: 'https://github.com/TYPO3/typo3/security/advisories/GHSA-q93m-25xv-94hh'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-47351'
  - url: >-
      https://github.com/TYPO3/typo3/commit/2740707563343d78184c0b7c6303a7484553d7f3
  - url: >-
      https://github.com/TYPO3/typo3/commit/932fbb9fcea25094e8bcc0f0ec5aab56b1d92451
  - url: >-
      https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-47351.yaml
  - url: 'https://typo3.org/security/advisory/typo3-core-sa-2026-014'
  - url: 'https://github.com/advisories/GHSA-q93m-25xv-94hh'
tags:
  - ghsa
  - composer
epss: 0.00238
epssPercentile: 0.15107
ingestedAt: '2026-07-07T15:41:59.201Z'
---

## Overview

### Problem
Backend users were able to insert arbitrary records and files into the TYPO3 clipboard without proper read permission checks, which allowed users to gather information about records and files they were not authorized to view.

### 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 Vincent Yang for reporting this issue, and to TYPO3 security team member Elias Häußler for fixing it.

### Resources
* [TYPO3-CORE-SA-2026-014](https://typo3.org/security/advisory/typo3-core-sa-2026-014)

## 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`