# CVE-2024-47617: Reflected XSS Vulnerability in Sulu Media Bundle

> Attackers can inject arbitrary HTML/JavaScript via media download URLs in Sulu CMS, potentially stealing data or hijacking user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Oct 2024
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-6784-9c82-vr85

## What is CVE-2024-47617?

CVE-2024-47617 is a medium-severity cross-site scripting vulnerability in sulu, published on 3 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Sulu is a PHP content management system. This vulnerability allows an attacker to inject arbitrary HTML/JavaScript code through the media download URL in Sulu CMS. It affects the SuluMediaBundle component. The vulnerability is a Reflected Cross-Site Scripting (XSS) issue, which could potentially allow attackers to steal sensitive information, manipulate the website's content, or perform actions on behalf of the victim. This vulnerability is fixed in 2.6.5 and 2.5.21.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

4 open source packages ship an affected version, including sulu/sulu. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sulu/sulu` | Packagist | From 2.0.0 | 2.5.21 |
| `sulu/sulu` | Packagist | From 2.0.0 | 2.5.21 |
| `sulu/sulu` | Packagist | From 2.6.0 | 2.6.5 |
| `sulu/sulu` | Packagist | From 2.6.0 | 2.6.5 |

Products: Sulu Sulu.

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

Upgrade sulu/sulu to a fixed version for your release line: 2.5.21 or 2.6.5.

## Is CVE-2024-47617 being exploited?

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

## Other vulnerabilities in sulu

- [CVE-2021-43836](https://insights.sbomify.com/CVE-2021-43836/): PHP file inclusion in the Sulu admin panel (high 8.5)
- [CVE-2021-32737](https://insights.sbomify.com/CVE-2021-32737/): XSS Injection in Media Collection Title was possible (high 8.4)
- [CVE-2021-43835](https://insights.sbomify.com/CVE-2021-43835/): Privilege escalation in the Sulu Admin panel (high 7.2)
- [CVE-2024-27915](https://insights.sbomify.com/CVE-2024-27915/): Sulu grants access to pages regardless of role permissions (medium 6.8)
- [CVE-2021-41169](https://insights.sbomify.com/CVE-2021-41169/): Improper Neutralization HTML tags in sulu/sulu (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47617 is a medium-severity cross-site scripting vulnerability in sulu, published on 3 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-47617 in the wild and no public exploit code.

Affected packages and fixed versions:
- sulu/sulu (Packagist): affected from 2.0.0; fixed in 2.5.21
- sulu/sulu (Packagist): affected from 2.0.0; fixed in 2.5.21
- sulu/sulu (Packagist): affected from 2.6.0; fixed in 2.6.5
- sulu/sulu (Packagist): affected from 2.6.0; fixed in 2.6.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/CVE-2024-47617/ (Markdown: https://insights.sbomify.com/CVE-2024-47617/index.md)
```

## Sources

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

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