# GHSA-gwfx-p7mr-f92v: Missing Access Check in TYPO3 CMS

> Attackers with limited access can bypass authorization checks to execute arbitrary Extbase actions, leading to information disclosure or remote code execution.

- **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:** 5 Jun 2024

## What is GHSA-gwfx-p7mr-f92v?

GHSA-gwfx-p7mr-f92v is a missing authorization vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Extbase request handling fails to implement a proper access check for requested controller/ action combinations, which makes it possible for an attacker to execute arbitrary Extbase actions by crafting a special request. To successfully exploit this vulnerability, an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation. The missing access check inevitably leads to information disclosure or remote code execution, depending on the action that an attacker is able to execute.

## Which versions are affected by GHSA-gwfx-p7mr-f92v?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.25 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.25 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.8 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.8 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.1.1 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.1.1 |

## How do I fix GHSA-gwfx-p7mr-f92v?

Upgrade typo3/cms to a fixed version for your release line: 6.2.25, 7.6.8 or 8.1.1.

## Is GHSA-gwfx-p7mr-f92v being exploited?

There is no known exploitation of GHSA-gwfx-p7mr-f92v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-gwfx-p7mr-f92v and fix it if it is affected.

What it is: GHSA-gwfx-p7mr-f92v is a missing authorization vulnerability in typo3/cms, published on 5 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-gwfx-p7mr-f92v in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.25
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.25
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.8
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.8
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.1.1
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.1.1

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-gwfx-p7mr-f92v/ (Markdown: https://insights.sbomify.com/GHSA-gwfx-p7mr-f92v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-gwfx-p7mr-f92v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-gwfx-p7mr-f92v/
Summaries are generated and may contain mistakes; the official description above is the record.