# GHSA-772m-43f3-hmf8: TYPO3 Broken Access Control in Localization Handling

> Limited-access backend users can modify or create pages in the default language, bypassing intended localization restrictions.

- **Severity:** Not scored
- **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:** 7 Jun 2024

## What is GHSA-772m-43f3-hmf8?

GHSA-772m-43f3-hmf8 is a missing authorization vulnerability in typo3/cms, published on 7 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It has been discovered that backend users having limited access to specific languages are capable of modifying and creating pages in the default language which actually should be disallowed. A valid backend user account is needed in order to exploit this vulnerability.

## Which versions are affected by GHSA-772m-43f3-hmf8?

2 open source packages ship an affected version, including typo3/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.23 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.23 |

## How do I fix GHSA-772m-43f3-hmf8?

Upgrade typo3/cms to 8.7.23 or later.

## Is GHSA-772m-43f3-hmf8 being exploited?

There is no known exploitation of GHSA-772m-43f3-hmf8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-772m-43f3-hmf8 and fix it if it is affected.

What it is: GHSA-772m-43f3-hmf8 is a missing authorization vulnerability in typo3/cms, published on 7 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-772m-43f3-hmf8 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.23
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.23

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/GHSA-772m-43f3-hmf8/ (Markdown: https://insights.sbomify.com/GHSA-772m-43f3-hmf8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-772m-43f3-hmf8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-772m-43f3-hmf8/
Summaries are generated and may contain mistakes; the official description above is the record.