# CVE-2024-13209: Redaxo CMS Structure Management Page index.php cross site scripting

> Attackers can inject malicious scripts via the Article Name field in Redaxo CMS structure management, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jan 2025
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-7wj8-856p-qc9m

## What is CVE-2024-13209?

CVE-2024-13209 is a medium-severity cross-site scripting vulnerability in Redaxo CMS, published on 9 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in Redaxo CMS 5.18.1. It has been classified as problematic. Affected is an unknown function of the file /index.php?page=structure&category_id=1&article_id=1&clang=1&function=edit_art&artstart=0 of the component Structure Management Page. The manipulation of the argument Article Name leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including redaxo/source. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redaxo/source` | Packagist | From 5.12.0-beta1 | 5.18.2 |
| `redaxo/source` | Packagist | From 5.12.0-beta1 | 5.18.2 |

Products: Redaxo Redaxo.

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

Upgrade redaxo/source to 5.18.2 or later.

## Is CVE-2024-13209 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13209 exists.

## Other vulnerabilities in Redaxo CMS

- [CVE-2018-18200](https://insights.sbomify.com/CVE-2018-18200/): SQL injection in n/a (critical 9.8)
- [CVE-2018-17831](https://insights.sbomify.com/CVE-2018-17831/): SQL injection in n/a (critical 9.8)
- [CVE-2026-21857](https://insights.sbomify.com/CVE-2026-21857/): Redaxo has Path Traversal in Backup Addon Leading to Arbitrary File Read (high 8.3)
- [CVE-2006-2843](https://insights.sbomify.com/CVE-2006-2843/): Code injection in n/a (high 7.5)
- [CVE-2006-2844](https://insights.sbomify.com/CVE-2006-2844/): Multiple PHP remote file inclusion vulnerabilities in Redaxo 3.0 allow remote attackers to execute arbitrary PHP code via a URL in the REX[I (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13209 is a medium-severity cross-site scripting vulnerability in Redaxo CMS, published on 9 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13209 exists.

Affected packages and fixed versions:
- redaxo/source (Packagist): affected from 5.12.0-beta1; fixed in 5.18.2
- redaxo/source (Packagist): affected from 5.12.0-beta1; fixed in 5.18.2

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

## Sources

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

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