Is CVE-2026-47350 exploited in the wild?

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

How severe is CVE-2026-47350?

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

Which products and versions are affected?

typo3/cms-core (Packagist) ECOSYSTEM:introduced=13.0.0,fixed=13.4.31; TYPO3 Association TYPO3 CMS >= 13.0.0, = 14.0.0, < 14.3.3.

Is there a fix for CVE-2026-47350?

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

How is CVE-2026-47350 attacked?

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

Am I affected by CVE-2026-47350?

Check whether you run typo3/cms-core (Packagist) or TYPO3 Association TYPO3 CMS 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-47350: TYPO3 CMS broken access control in DataHandler

Q: Is there a fix for CVE-2026-47350?

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

Q: How is CVE-2026-47350 attacked?

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

Q: Am I affected by CVE-2026-47350?

Check whether you run typo3/cms-core (Packagist) or TYPO3 Association TYPO3 CMS 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-47350 · Severity: medium · CVSS 4 · Published 2026-06-09

TYPO3 CMS is a popular enterprise content management system. A security flaw in its data handling component allowed authorized backend users to move content records between pages even if they did not have permission to edit the original source page. This could lead to unauthorized modification of website structure or content organization by users with limited access.

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

Quick answers

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

Technical details

A broken access control vulnerability (CWE-862) exists in the TYPO3 DataHandler's moveRecord() function. Following a refactoring in a previous version, a critical authorization check was omitted, failing to verify if a backend user possessed edit permissions on the source page before executing a move operation. An authenticated backend user with low privileges can exploit this to relocate records to different pages across the CMS. The issue is resolved in TYPO3 versions 13.4.31 and 14.3.3 by re-implementing the missing permission check.

Affected products

TYPO3 TYPO3 CMS >= 13.0.0, < 13.4.31; >= 14.0.0, < 14.3.3

Identifiers

CVE-2026-47350
GHSA-qcmw-6rm2-5x78

Timeline

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

References

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