Is CVE-2026-47349 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47349 being exploited in the wild.

How severe is CVE-2026-47349?

Medium severity, with a CVSS score of 4, published 9 June 2026.

Which products and versions are affected?

typo3/cms-core (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57; typo3/cms-recycler (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57.

Is there a fix for CVE-2026-47349?

Yes. typo3/cms-core (Packagist): upgrade to 10.4.57 or later; typo3/cms-recycler (Packagist): upgrade to 10.4.57 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47349 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-47349?

Check whether you run typo3/cms-core (Packagist) or typo3/cms-recycler (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47349: TYPO3 CMS missing authorization in Recycler module

CVE-2026-47349 · Severity: medium · CVSS 4 · Published 2026-06-09

TYPO3 CMS, a popular content management system, contains a security flaw in its Recycler module. This module allows administrators to manage and restore deleted content. An exploit allows lower-privileged backend users to restore deleted records they are not supposed to access, potentially leading to unauthorized content modification or data recovery.

Technologies: typo3/cms-core (Packagist), typo3/cms-recycler (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-47349 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47349 being exploited in the wild.
How severe is CVE-2026-47349?: Medium severity, with a CVSS score of 4, published 9 June 2026.
Which products and versions are affected?: typo3/cms-core (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57; typo3/cms-recycler (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57.
Is there a fix for CVE-2026-47349?: Yes. typo3/cms-core (Packagist): upgrade to 10.4.57 or later; typo3/cms-recycler (Packagist): upgrade to 10.4.57 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47349 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47349?: Check whether you run typo3/cms-core (Packagist) or typo3/cms-recycler (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

typo3/cms-core (Packagist): upgrade to 10.4.57 or later
```
composer require typo3/cms-core:^10.4.57
```
typo3/cms-recycler (Packagist): upgrade to 10.4.57 or later
```
composer require typo3/cms-recycler:^10.4.57
```

Technical details

A missing authorization check (CWE-862) exists in the TYPO3 Recycler module. Backend users with legitimate access to the Recycler module can bypass intended permission restrictions to restore soft-deleted records on pages or within tables for which they lack modification rights. This is a network-based attack requiring 'Low' privileges (backend user account). The vulnerability has been addressed in TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, and 14.3.3 LTS.

Affected products

TYPO3 TYPO3 CMS < 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30, 14.0.0-14.3.2

Identifiers

CVE-2026-47349
GHSA-f34x-rx2w-7pm3

Timeline

2026-06-09: disclosed
2026-06-09: patched
2026-06-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.