# GHSA-h934-f4m4-wc8x: Typo3 Information Disclosure in Page Tree

> Authenticated backend users can view unauthorized pages in the page tree, leading to information disclosure.

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

## What is GHSA-h934-f4m4-wc8x?

GHSA-h934-f4m4-wc8x is a vulnerability in typo3/cms, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It has been discovered backend users not having read access to specific pages still could see them in the page tree which actually should be disallowed. A valid backend user account is needed in order to exploit this vulnerability.

## Which versions are affected by GHSA-h934-f4m4-wc8x?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 9.0.0 | 9.5.6 |
| `typo3/cms` | Packagist | From 9.0.0 | 9.5.6 |

## How do I fix GHSA-h934-f4m4-wc8x?

Upgrade typo3/cms to 9.5.6 or later.

## Is GHSA-h934-f4m4-wc8x being exploited?

There is no known exploitation of GHSA-h934-f4m4-wc8x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-h934-f4m4-wc8x and fix it if it is affected.

What it is: GHSA-h934-f4m4-wc8x is a vulnerability in typo3/cms, published on 5 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-h934-f4m4-wc8x in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.6
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.6

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-h934-f4m4-wc8x/ (Markdown: https://insights.sbomify.com/GHSA-h934-f4m4-wc8x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-h934-f4m4-wc8x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-h934-f4m4-wc8x/
Summaries are generated and may contain mistakes; the official description above is the record.