# GHSA-95qm-3xp7-vfj5: TYPO3 Cross-Site Scripting in Form Framework validation handling

> An attacker can inject malicious scripts via form validation errors, potentially stealing user data or hijacking sessions in TYPO3 installations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-95qm-3xp7-vfj5?

GHSA-95qm-3xp7-vfj5 is a cross-site scripting vulnerability in typo3/cms-core, published on 30 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

It has been discovered that the output of field validation errors in the Form Framework is vulnerable to cross-site scripting.

## Which versions are affected by GHSA-95qm-3xp7-vfj5?

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


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

## How do I fix GHSA-95qm-3xp7-vfj5?

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

## Is GHSA-95qm-3xp7-vfj5 being exploited?

There is no known exploitation of GHSA-95qm-3xp7-vfj5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-95qm-3xp7-vfj5 and fix it if it is affected.

What it is: GHSA-95qm-3xp7-vfj5 is a cross-site scripting vulnerability in typo3/cms-core, published on 30 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-95qm-3xp7-vfj5 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.2.1
- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.2.1
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.30
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.30
- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.12
- typo3/cms-core (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-95qm-3xp7-vfj5/ (Markdown: https://insights.sbomify.com/GHSA-95qm-3xp7-vfj5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-95qm-3xp7-vfj5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-95qm-3xp7-vfj5/
Summaries are generated and may contain mistakes; the official description above is the record.