Is CVE-2026-47352 exploited in the wild?

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

How severe is CVE-2026-47352?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-47352?

Yes. typo3/cms-backend (Packagist): upgrade to 10.4.57 or later; typo3/cms-core (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-47352 attacked?

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

Am I affected by CVE-2026-47352?

Check whether you run typo3/cms-backend (Packagist) or typo3/cms-core (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-47352: TYPO3 CMS broken access control in Backend API

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

TYPO3 CMS, a popular enterprise content management system, contains a security flaw in its administrative backend. This vulnerability allows logged-in staff members to view information about files they are not authorized to see, potentially exposing sensitive metadata or file structures. Organizations should update to the latest patched versions to ensure internal access controls are properly enforced.

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

Quick answers

Is CVE-2026-47352 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47352 being exploited in the wild.
How severe is CVE-2026-47352?: Medium severity, with a CVSS score of 4, published 9 June 2026.
Which products and versions are affected?: typo3/cms-backend (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57; typo3/cms-core (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57.
Is there a fix for CVE-2026-47352?: Yes. typo3/cms-backend (Packagist): upgrade to 10.4.57 or later; typo3/cms-core (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-47352 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47352?: Check whether you run typo3/cms-backend (Packagist) or typo3/cms-core (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-backend (Packagist): upgrade to 10.4.57 or later
```
composer require typo3/cms-backend:^10.4.57
```
typo3/cms-core (Packagist): upgrade to 10.4.57 or later
```
composer require typo3/cms-core:^10.4.57
```

Technical details

A missing authorization vulnerability (CWE-862) exists in several TYPO3 Backend API routes. The root cause is a failure to perform proper permission checks when retrieving file metadata, allowing an authenticated backend user to bypass configured file mounts or storage restrictions. An attacker with low-level backend privileges can exploit this over the network to access metadata for files they should not be able to view. The issue is resolved 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-47352
GHSA-2j54-93q2-3hjq

Timeline

2026-06-09: disclosed: Initial disclosure by TYPO3 and NVD publication
2026-06-12: advisory: GitHub Advisory published and reviewed

References

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