# GHSA-x428-565f-8xj2: TYPO3 Arbitrary Code Execution and Cross-Site Scripting in Backend API

> Authenticated backend users can execute arbitrary code or inject scripts via TSconfig fields in TYPO3.

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

## What is GHSA-x428-565f-8xj2?

GHSA-x428-565f-8xj2 is a code injection vulnerability in typo3/cms-core, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Backend API configuration using Page TSconfig is vulnerable to arbitrary code execution and cross-site scripting. TSconfig fields of page properties in backend forms can be used to inject malicious sequences. Field tsconfig_includes is vulnerable to directory traversal leading to same scenarios as having direct access to TSconfig settings.

A valid backend user account having access to modify values for fields `pages.TSconfig` and `pages.tsconfig_includes` is needed in order to exploit this vulnerability.

## Which versions are affected by GHSA-x428-565f-8xj2?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.27 |
| `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.27 |
| `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.8 |
| `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.8 |

## How do I fix GHSA-x428-565f-8xj2?

Upgrade typo3/cms-core to a fixed version for your release line: 8.7.27 or 9.5.8.

## Is GHSA-x428-565f-8xj2 being exploited?

There is no known exploitation of GHSA-x428-565f-8xj2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x428-565f-8xj2 and fix it if it is affected.

What it is: GHSA-x428-565f-8xj2 is a code injection vulnerability in typo3/cms-core, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-x428-565f-8xj2 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.27
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.27
- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.8
- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.8

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-x428-565f-8xj2/ (Markdown: https://insights.sbomify.com/GHSA-x428-565f-8xj2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x428-565f-8xj2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x428-565f-8xj2/
Summaries are generated and may contain mistakes; the official description above is the record.