# GHSA-g776-759r-pf6x: TYPO3 Broken Access Control in Import Module

> Regular backend users can bypass access controls in the Import module to upload files, potentially leading to privilege escalation and SQL injection.

- **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-g776-759r-pf6x?

GHSA-g776-759r-pf6x is a missing authorization 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

It has been discovered that the Import/Export module is susceptible to broken access control. Regular backend users have access to import functionality which usually only is available to admin users or users having User TSconfig setting options.impexp.enableImportForNonAdminUser explicitly enabled.

Database content to be imported however was correctly checked against users’ permissions and not affected. However it was possible to upload files by-passing restrictions of the file abstraction layer (FAL) - however this did not affect executable files which have been correctly secured by fileDenyPattern.

Currently the only known vulnerability is to directly inject *.form.yaml files which could be used to trigger the vulnerability of TYPO3-CORE-SA-2018-003 (privilege escalation & SQL injection) - which requires the Form Framework (ext:form) being available on an according website. CVSSv3 scoring is based on this scenario.

A valid backend user account is needed in order to exploit this vulnerability.

## Which versions are affected by GHSA-g776-759r-pf6x?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms-core` | Packagist | From 9.3.0 | 9.5.8 |
| `typo3/cms-core` | Packagist | From 9.3.0 | 9.5.8 |

## How do I fix GHSA-g776-759r-pf6x?

Upgrade typo3/cms-core to 9.5.8 or later.

## Is GHSA-g776-759r-pf6x being exploited?

There is no known exploitation of GHSA-g776-759r-pf6x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g776-759r-pf6x and fix it if it is affected.

What it is: GHSA-g776-759r-pf6x is a missing authorization 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-g776-759r-pf6x in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 9.3.0; fixed in 9.5.8
- typo3/cms-core (Packagist): affected from 9.3.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-g776-759r-pf6x/ (Markdown: https://insights.sbomify.com/GHSA-g776-759r-pf6x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g776-759r-pf6x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g776-759r-pf6x/
Summaries are generated and may contain mistakes; the official description above is the record.