# GHSA-wq43-8r5p-w3mc: contao/core PHP object injection vulnerability allows for arbitrary code execution

> Untrusted data passed to deserialize() in Contao allows PHP object injection, leading to arbitrary code execution.

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

## What is GHSA-wq43-8r5p-w3mc?

GHSA-wq43-8r5p-w3mc is an unsafe deserialization vulnerability in contao/core, published on 15 May 2024. It can be exploited over the network.

### Official description

PHP object injection vulnerability was identified in contao/core due to untrusted data being passed to `deserialize()` function.

## Which versions are affected by GHSA-wq43-8r5p-w3mc?

4 open source packages ship an affected version, including contao/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `contao/core` | Packagist | From 2.0.0 | 2.11.14 |
| `contao/core` | Packagist | From 2.0.0 | 2.11.14 |
| `contao/core` | Packagist | From 3.0.0 | 3.2.5 |
| `contao/core` | Packagist | From 3.0.0 | 3.2.5 |

## How do I fix GHSA-wq43-8r5p-w3mc?

Upgrade contao/core to a fixed version for your release line: 2.11.14 or 3.2.5.

## Is GHSA-wq43-8r5p-w3mc being exploited?

There is no known exploitation of GHSA-wq43-8r5p-w3mc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wq43-8r5p-w3mc and fix it if it is affected.

What it is: GHSA-wq43-8r5p-w3mc is an unsafe deserialization vulnerability in contao/core, published on 15 May 2024. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-wq43-8r5p-w3mc in the wild and no public exploit code.

Affected packages and fixed versions:
- contao/core (Packagist): affected from 2.0.0; fixed in 2.11.14
- contao/core (Packagist): affected from 2.0.0; fixed in 2.11.14
- contao/core (Packagist): affected from 3.0.0; fixed in 3.2.5
- contao/core (Packagist): affected from 3.0.0; fixed in 3.2.5

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-wq43-8r5p-w3mc/ (Markdown: https://insights.sbomify.com/GHSA-wq43-8r5p-w3mc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wq43-8r5p-w3mc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wq43-8r5p-w3mc/
Summaries are generated and may contain mistakes; the official description above is the record.