# CVE-2024-45398: Remote command execution through file upload in contao/core-bundle

> A back end user with file manager access can upload malicious files to execute arbitrary code on the server.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **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:** 17 Sep 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-vm6r-j788-hjh5

## What is CVE-2024-45398?

CVE-2024-45398 is a high-severity vulnerability in contao, published on 17 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Contao is an Open Source CMS. In affected versions a back end user with access to the file manager can upload malicious files and execute them on the server. Users are advised to update to Contao 4.13.49, 5.3.15 or 5.4.3. Users unable to update are advised to configure their web server so it does not execute PHP files and other scripts in the Contao file upload directory.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-45398?

6 open source packages ship an affected version, including contao/core-bundle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `contao/core-bundle` | Packagist | From 4.0.0 | 4.13.49 |
| `contao/core-bundle` | Packagist | From 4.0.0 | 4.13.49 |
| `contao/core-bundle` | Packagist | From 5.0.0 | 5.3.15 |
| `contao/core-bundle` | Packagist | From 5.0.0 | 5.3.15 |
| `contao/core-bundle` | Packagist | From 5.4.0 | 5.4.3 |
| `contao/core-bundle` | Packagist | From 5.4.0 | 5.4.3 |

Products: Contao Contao.

## How do I fix CVE-2024-45398?

Upgrade contao/core-bundle to a fixed version for your release line: 4.13.49, 5.3.15 or 5.4.3.

## Is CVE-2024-45398 being exploited?

There is no known exploitation of CVE-2024-45398 in the wild and no public exploit code.

## Other vulnerabilities in contao

- [CVE-2022-26265](https://insights.sbomify.com/CVE-2022-26265/): Remote Code Execution in Contao Managed Edition (critical 9.8)
- [CVE-2019-11512](https://insights.sbomify.com/CVE-2019-11512/): Contao SQL injection in the file manager (critical 9.8)
- [CVE-2012-4383](https://insights.sbomify.com/CVE-2012-4383/): Contao core SQL Injection Vulnerability (high 8.8)
- [CVE-2019-19745](https://insights.sbomify.com/CVE-2019-19745/): Unrestricted file uploads in Contao (high 8.8)
- [CVE-2024-28235](https://insights.sbomify.com/CVE-2024-28235/): Contao possible cookie sharing with external domains while checking protected pages for broken links (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45398 and fix it if it is affected.

What it is: CVE-2024-45398 is a high-severity vulnerability in contao, published on 17 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45398 in the wild and no public exploit code.

Affected packages and fixed versions:
- contao/core-bundle (Packagist): affected from 4.0.0; fixed in 4.13.49
- contao/core-bundle (Packagist): affected from 4.0.0; fixed in 4.13.49
- contao/core-bundle (Packagist): affected from 5.0.0; fixed in 5.3.15
- contao/core-bundle (Packagist): affected from 5.0.0; fixed in 5.3.15
- contao/core-bundle (Packagist): affected from 5.4.0; fixed in 5.4.3
- contao/core-bundle (Packagist): affected from 5.4.0; fixed in 5.4.3

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/CVE-2024-45398/ (Markdown: https://insights.sbomify.com/CVE-2024-45398/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45398
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45398
- OSV: https://osv.dev/vulnerability/CVE-2024-45398

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45398/
Summaries are generated and may contain mistakes; the official description above is the record.