# GHSA-wrpf-2x8h-82gr: Typo3 Arbitrary File Disclosure in Form Component

> Authenticated backend users can disclose arbitrary files via vulnerable form upload 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:** 4 Jun 2024

## What is GHSA-wrpf-2x8h-82gr?

GHSA-wrpf-2x8h-82gr is a path traversal vulnerability in typo3/cms, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Failing to properly validate user input, the form component is susceptible to Arbitrary File Disclosure. A valid backend user account is needed to exploit this vulnerability. Only forms are vulnerable, which contain upload fields.

## Which versions are affected by GHSA-wrpf-2x8h-82gr?

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.20 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.20 |

## How do I fix GHSA-wrpf-2x8h-82gr?

Upgrade typo3/cms to 6.2.20 or later.

## Is GHSA-wrpf-2x8h-82gr being exploited?

There is no known exploitation of GHSA-wrpf-2x8h-82gr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wrpf-2x8h-82gr and fix it if it is affected.

What it is: GHSA-wrpf-2x8h-82gr is a path traversal vulnerability in typo3/cms, published on 4 Jun 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-wrpf-2x8h-82gr 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.20
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.20

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-wrpf-2x8h-82gr/ (Markdown: https://insights.sbomify.com/GHSA-wrpf-2x8h-82gr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wrpf-2x8h-82gr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wrpf-2x8h-82gr/
Summaries are generated and may contain mistakes; the official description above is the record.