---
id: CVE-2026-47349
aliases:
  - GHSA-f34x-rx2w-7pm3
title: TYPO3 CMS has Broken Access Control in the Recycler Module
summary: TYPO3 CMS has Broken Access Control in the Recycler Module
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-recycler < 10.4.57
  - 'typo3/cms-recycler >= 11.0.0, < 11.5.51'
  - 'typo3/cms-recycler >= 12.0.0, < 12.4.46'
  - 'typo3/cms-recycler >= 13.0.0, < 13.4.31'
  - 'typo3/cms-recycler >= 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-recycler 10.4.57
  - typo3/cms-recycler 11.5.51
  - typo3/cms-recycler 12.4.46
  - typo3/cms-recycler 13.4.31
  - typo3/cms-recycler 14.3.3
published: '2026-06-12'
updated: '2026-06-12'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-f34x-rx2w-7pm3'
references:
  - url: 'https://github.com/TYPO3/typo3/security/advisories/GHSA-f34x-rx2w-7pm3'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-47349'
  - url: >-
      https://github.com/TYPO3/typo3/commit/92f08d8944f1aeccf506fcd323c260448c64d7c8
  - url: >-
      https://github.com/TYPO3/typo3/commit/9f17a307cf774d63ab8291fc97c6b55653b4265a
  - url: >-
      https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-47349.yaml
  - url: 'https://typo3.org/security/advisory/typo3-core-sa-2026-011'
  - url: 'https://github.com/advisories/GHSA-f34x-rx2w-7pm3'
tags:
  - ghsa
  - composer
epss: 0.00414
epssPercentile: 0.3287
ingestedAt: '2026-07-07T15:41:59.009Z'
---

## Overview

### Problem
Backend users with access to the Recycler module were able to restore soft-deleted records on pages or for tables they were not authorized to modify.

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

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

## 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-recycler < 10.4.57`
- `typo3/cms-recycler >= 11.0.0, < 11.5.51`
- `typo3/cms-recycler >= 12.0.0, < 12.4.46`
- `typo3/cms-recycler >= 13.0.0, < 13.4.31`
- `typo3/cms-recycler >= 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-recycler 10.4.57`
- `typo3/cms-recycler 11.5.51`
- `typo3/cms-recycler 12.4.46`
- `typo3/cms-recycler 13.4.31`
- `typo3/cms-recycler 14.3.3`