# GHSA-f9hr-7cfq-mjg2: TYPO3 Arbitrary Code Execution via File List Module

> Authenticated backend users can upload executable files like .phar or .cgi to achieve remote code execution if the web server is configured to handle these extensions.

- **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:** 30 May 2024

## What is GHSA-f9hr-7cfq-mjg2?

GHSA-f9hr-7cfq-mjg2 is a vulnerability in typo3/cms-core, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to missing file extensions in $GLOBALS['TYPO3_CONF_VARS']['BE'][‘fileDenyPattern’], backend users are allowed to upload *.phar, *.shtml, *.pl or *.cgi files which can be executed in certain web server setups. A valid backend user account is needed in order to exploit this vulnerability.

Derivatives of Debian GNU Linux are handling *.phar files as PHP applications since PHP 7.1 (for unofficial packages) and PHP 7.2 (for official packages).

The file extension *.shtml is bound to server side includes which are not enabled per default in most common Linux based distributions. File extension *.pl and *.cgi require additional handlers to be configured which is also not the case in most common distributions (except for /cgi-bin/ location).

## Which versions are affected by GHSA-f9hr-7cfq-mjg2?

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


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

## How do I fix GHSA-f9hr-7cfq-mjg2?

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

## Is GHSA-f9hr-7cfq-mjg2 being exploited?

There is no known exploitation of GHSA-f9hr-7cfq-mjg2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f9hr-7cfq-mjg2 and fix it if it is affected.

What it is: GHSA-f9hr-7cfq-mjg2 is a vulnerability in typo3/cms-core, published on 30 May 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-f9hr-7cfq-mjg2 in the wild and no public exploit code.

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

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-f9hr-7cfq-mjg2/ (Markdown: https://insights.sbomify.com/GHSA-f9hr-7cfq-mjg2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f9hr-7cfq-mjg2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f9hr-7cfq-mjg2/
Summaries are generated and may contain mistakes; the official description above is the record.