# CVE-2026-47350: TYPO3 CMS - Broken Access Control in DataHandler

> Backend users can move records to different pages without edit permissions on the source page, allowing unauthorized data modification.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-qcmw-6rm2-5x78

## What is CVE-2026-47350?

CVE-2026-47350 is a medium-severity missing authorization vulnerability in TYPO3 CMS, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Backend users were able to move records to a different page without having edit permissions on the source page. This issue affects TYPO3 CMS versions 13.0.0-13.4.30 and 14.0.0-14.3.2.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-47350?

4 open source packages ship an affected version, including typo3/cms-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.31 |
| `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.31 |
| `typo3/cms-core` | Packagist | From 14.0.0 | 14.3.3 |
| `typo3/cms-core` | Packagist | From 14.0.0 | 14.3.3 |

## How do I fix CVE-2026-47350?

Upgrade typo3/cms-core to a fixed version for your release line: 13.4.31 or 14.3.3.

## Is CVE-2026-47350 being exploited?

There is no known exploitation of CVE-2026-47350 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47350 and fix it if it is affected.

What it is: CVE-2026-47350 is a medium-severity missing authorization vulnerability in TYPO3 CMS, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47350 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.31
- typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.31
- typo3/cms-core (Packagist): affected from 14.0.0; fixed in 14.3.3
- typo3/cms-core (Packagist): affected from 14.0.0; fixed in 14.3.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47350/ (Markdown: https://insights.sbomify.com/CVE-2026-47350/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47350
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47350
- OSV: https://osv.dev/vulnerability/CVE-2026-47350

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47350/
Summaries are generated and may contain mistakes; the official description above is the record.