# GHSA-qrxh-46mr-pr7q: TYPO3 is susceptible to Cross-Site Flashing

> An attacker can embed malicious flash videos from external domains in TYPO3, potentially leading to cross-site scripting attacks.

- **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:** 3 Jun 2024

## What is GHSA-qrxh-46mr-pr7q?

GHSA-qrxh-46mr-pr7q is a cross-site scripting vulnerability in typo3/cms, published on 3 Jun 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

The flashplayer misses to validate flash and image files. Therefore it is possible to embed flash videos from external domains.

## Which versions are affected by GHSA-qrxh-46mr-pr7q?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.16 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.16 |

## How do I fix GHSA-qrxh-46mr-pr7q?

Upgrade typo3/cms to 6.2.16 or later.

## Is GHSA-qrxh-46mr-pr7q being exploited?

There is no known exploitation of GHSA-qrxh-46mr-pr7q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qrxh-46mr-pr7q and fix it if it is affected.

What it is: GHSA-qrxh-46mr-pr7q is a cross-site scripting vulnerability in typo3/cms, published on 3 Jun 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-qrxh-46mr-pr7q 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.16
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.16

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-qrxh-46mr-pr7q/ (Markdown: https://insights.sbomify.com/GHSA-qrxh-46mr-pr7q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qrxh-46mr-pr7q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qrxh-46mr-pr7q/
Summaries are generated and may contain mistakes; the official description above is the record.