# GHSA-4r76-xr68-w7m7: TYPO3 may allow editors to change, create, or delete metadata of files not within their file mounts

> Editors can modify, create, or delete metadata for files outside their assigned file mounts, bypassing intended access restrictions.

- **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-4r76-xr68-w7m7?

GHSA-4r76-xr68-w7m7 is a missing authorization vulnerability in typo3/cms, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It has been discovered, that editors with access to file meta data table could change, create or delete metadata of files which are not within their file mounts.

## Which versions are affected by GHSA-4r76-xr68-w7m7?

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.14 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |

## How do I fix GHSA-4r76-xr68-w7m7?

Upgrade typo3/cms to a fixed version for your release line: 6.2.14 or 7.3.1.

## Is GHSA-4r76-xr68-w7m7 being exploited?

There is no known exploitation of GHSA-4r76-xr68-w7m7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4r76-xr68-w7m7 and fix it if it is affected.

What it is: GHSA-4r76-xr68-w7m7 is a missing authorization vulnerability in typo3/cms, 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-4r76-xr68-w7m7 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.14
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.14
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.1
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.1

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-4r76-xr68-w7m7/ (Markdown: https://insights.sbomify.com/GHSA-4r76-xr68-w7m7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4r76-xr68-w7m7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4r76-xr68-w7m7/
Summaries are generated and may contain mistakes; the official description above is the record.