# CVE-2024-45612: Insert tag injection via canonical URL in Contao

> An untrusted user can inject insert tags into the canonical URL, leading to potential code execution on the front end.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-2xpq-xp6c-5mgj

## What is CVE-2024-45612?

CVE-2024-45612 is a medium-severity cross-site scripting vulnerability in contao, published on 17 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Contao is an Open Source CMS. In affected versions an untrusted user can inject insert tags into the canonical tag, which are then replaced on the web page (front end). Users are advised to update to Contao 4.13.49, 5.3.15 or 5.4.3. Users unable to upgrade should disable canonical tags in the root page settings.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-20 (Improper Input Validation)

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

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.13.0 | 4.13.49 |
| `contao/core-bundle` | Packagist | From 4.13.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-45612?

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-45612 being exploited?

There is no known exploitation of CVE-2024-45612 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-45612 and fix it if it is affected.

What it is: CVE-2024-45612 is a medium-severity cross-site scripting vulnerability in contao, published on 17 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45612 in the wild and no public exploit code.

Affected packages and fixed versions:
- contao/core-bundle (Packagist): affected from 4.13.0; fixed in 4.13.49
- contao/core-bundle (Packagist): affected from 4.13.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-45612/ (Markdown: https://insights.sbomify.com/CVE-2024-45612/index.md)
```

## Sources

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

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