# GHSA-pqfv-97hj-g97g: TYPO3 Frontend vulnerable to Unauthenticated Path Disclosure

> Unauthenticated attackers can access a testing script to reveal the absolute server path of the TYPO3 installation.

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

## What is GHSA-pqfv-97hj-g97g?

GHSA-pqfv-97hj-g97g is a vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It has been discovered, that calling a PHP script which is delivered with TYPO3 for testing purposes, discloses the absolute server path to the TYPO3 installation.

## Which versions are affected by GHSA-pqfv-97hj-g97g?

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.15 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.15 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.4.0 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.4.0 |

## How do I fix GHSA-pqfv-97hj-g97g?

Upgrade typo3/cms to a fixed version for your release line: 6.2.15 or 7.4.0.

## Is GHSA-pqfv-97hj-g97g being exploited?

There is no known exploitation of GHSA-pqfv-97hj-g97g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-pqfv-97hj-g97g and fix it if it is affected.

What it is: GHSA-pqfv-97hj-g97g is a vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-pqfv-97hj-g97g 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.15
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.15
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.4.0
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.4.0

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-pqfv-97hj-g97g/ (Markdown: https://insights.sbomify.com/GHSA-pqfv-97hj-g97g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-pqfv-97hj-g97g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-pqfv-97hj-g97g/
Summaries are generated and may contain mistakes; the official description above is the record.