# GHSA-wp8j-c736-c5r3: TYPO3 Cross-Site Scripting Vulnerability Exploitable by Editors

> Editors can inject malicious scripts via typolink attributes or file renaming errors, potentially compromising frontend users or backend administrators.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 May 2024

## What is GHSA-wp8j-c736-c5r3?

GHSA-wp8j-c736-c5r3 is a cross-site scripting vulnerability in typo3/cms, published on 30 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

It has been discovered that link tags generated by typolink functionality in the website's frontend are vulnerable to cross-site scripting - values being assigned to HTML attributes have not been parsed correctly. A valid backend user account is needed to exploit this vulnerability.

As second and separate vulnerability in the filelist module of the backend user interface has been referenced with this advisory as well. Error messages being shown after using a malicious name for renaming a file are not propery encoded, thus vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.

## Which versions are affected by GHSA-wp8j-c736-c5r3?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |

## How do I fix GHSA-wp8j-c736-c5r3?

Upgrade typo3/cms to a fixed version for your release line: 6.2.14 or 7.3.1.

## Is GHSA-wp8j-c736-c5r3 being exploited?

There is no known exploitation of GHSA-wp8j-c736-c5r3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wp8j-c736-c5r3 and fix it if it is affected.

What it is: GHSA-wp8j-c736-c5r3 is a cross-site scripting vulnerability in typo3/cms, published on 30 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-wp8j-c736-c5r3 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.14
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.14
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.1
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.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-wp8j-c736-c5r3/ (Markdown: https://insights.sbomify.com/GHSA-wp8j-c736-c5r3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wp8j-c736-c5r3

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