# GHSA-g7hw-jh4p-75wr: TYPO3 Cross-Site Scripting in Filelist Module

> An attacker with file system access can inject malicious scripts into the TYPO3 backend file list, potentially compromising administrator accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Jun 2024

## What is GHSA-g7hw-jh4p-75wr?

GHSA-g7hw-jh4p-75wr is a cross-site scripting vulnerability in typo3/cms, published on 7 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

It has been discovered that the output table listing in the “Files” backend module is vulnerable to cross-site scripting when a file extension contains malicious sequences.

Access to the file system of the server - either directly or through synchronization - is required to exploit the vulnerability.

## Which versions are affected by GHSA-g7hw-jh4p-75wr?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 10.0.0 | 10.2.1 |
| `typo3/cms` | Packagist | From 10.0.0 | 10.2.1 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.30 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.30 |
| `typo3/cms` | Packagist | From 9.0.0 | 9.5.12 |
| `typo3/cms` | Packagist | From 9.0.0 | 9.5.12 |

## How do I fix GHSA-g7hw-jh4p-75wr?

Upgrade typo3/cms to a fixed version for your release line: 10.2.1, 8.7.30 or 9.5.12.

## Is GHSA-g7hw-jh4p-75wr being exploited?

There is no known exploitation of GHSA-g7hw-jh4p-75wr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g7hw-jh4p-75wr and fix it if it is affected.

What it is: GHSA-g7hw-jh4p-75wr is a cross-site scripting vulnerability in typo3/cms, published on 7 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-g7hw-jh4p-75wr in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.2.1
- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.2.1
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.30
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.30
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.12
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.12

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-g7hw-jh4p-75wr/ (Markdown: https://insights.sbomify.com/GHSA-g7hw-jh4p-75wr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g7hw-jh4p-75wr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g7hw-jh4p-75wr/
Summaries are generated and may contain mistakes; the official description above is the record.