# GHSA-67wg-6j7r-mqh8: Arbitrary Code Execution in TYPO3 CMS

> Backend users can upload executable .pht files due to missing deny patterns, leading to arbitrary code execution on vulnerable server configurations.

- **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-67wg-6j7r-mqh8?

GHSA-67wg-6j7r-mqh8 is a 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

Due to a missing file extension in the fileDenyPattern, backend user are allowed to upload *.pht files which can be executed in certain web server setups. The new default fileDenyPattern is the following, which might have been overridden in the TYPO3 Install Tool.
```
\.(php[3-7]?|phpsh|phtml|pht)(\..*)?$|^\.htaccess$
```

## Which versions are affected by GHSA-67wg-6j7r-mqh8?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.22 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.22 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.5 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.5 |

## How do I fix GHSA-67wg-6j7r-mqh8?

Upgrade typo3/cms to a fixed version for your release line: 7.6.22 or 8.7.5.

## Is GHSA-67wg-6j7r-mqh8 being exploited?

There is no known exploitation of GHSA-67wg-6j7r-mqh8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-67wg-6j7r-mqh8 and fix it if it is affected.

What it is: GHSA-67wg-6j7r-mqh8 is a 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-67wg-6j7r-mqh8 in the wild and no public exploit code.

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

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-67wg-6j7r-mqh8/ (Markdown: https://insights.sbomify.com/GHSA-67wg-6j7r-mqh8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-67wg-6j7r-mqh8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-67wg-6j7r-mqh8/
Summaries are generated and may contain mistakes; the official description above is the record.