# GHSA-8j9v-4hhh-x43c: Cross-Site Scripting (XSS) in TYPO3 component CSS styled content

> Authenticated editors can inject arbitrary HTML or JavaScript via the CSS styled content component due to improper input encoding.

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

## What is GHSA-8j9v-4hhh-x43c?

GHSA-8j9v-4hhh-x43c is a cross-site scripting vulnerability in typo3/cms, published on 4 Jun 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

Failing to properly encode user input, the CSS styled content component is susceptible to Cross-Site Scripting, allowing authenticated editors to inject arbitrary HTML or JavaScript.

## Which versions are affected by GHSA-8j9v-4hhh-x43c?

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.19 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.19 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.4 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.4 |

## How do I fix GHSA-8j9v-4hhh-x43c?

Upgrade typo3/cms to a fixed version for your release line: 6.2.19 or 7.6.4.

## Is GHSA-8j9v-4hhh-x43c being exploited?

There is no known exploitation of GHSA-8j9v-4hhh-x43c in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8j9v-4hhh-x43c and fix it if it is affected.

What it is: GHSA-8j9v-4hhh-x43c is a cross-site scripting vulnerability in typo3/cms, published on 4 Jun 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-8j9v-4hhh-x43c 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.19
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.19
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.4
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.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-8j9v-4hhh-x43c/ (Markdown: https://insights.sbomify.com/GHSA-8j9v-4hhh-x43c/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8j9v-4hhh-x43c

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8j9v-4hhh-x43c/
Summaries are generated and may contain mistakes; the official description above is the record.