# CVE-2025-47778: Sulu vulnerable to XXE in SVG File upload Inspector

> An admin user can upload malicious SVG files to trigger XML External Entity attacks, potentially reading sensitive data or causing denial of service.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2025
- **Updated:** 14 May 2025
- **Also known as:** GHSA-f6rx-hf55-4255

## What is CVE-2025-47778?

CVE-2025-47778 is a medium-severity vulnerability in sulu, published on 14 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Sulu is an open-source PHP content management system based on the Symfony framework. Starting in versions 2.5.21, 2.6.5, and 3.0.0-alpha1, an admin user can upload SVG which may load external data via XML DOM library. This can be used for insecure XML External Entity References. The problem has been patched in versions 2.6.9, 2.5.25, and 3.0.0-alpha3. As a workaround, one may patch the effect file `src/Sulu/Bundle/MediaBundle/FileInspector/SvgFileInspector.php` manually.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2025-47778?

6 open source packages ship an affected version, including sulu/sulu.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sulu/sulu` | Packagist | From 2.5.21 | 2.5.25 |
| `sulu/sulu` | Packagist | From 2.5.21 | 2.5.25 |
| `sulu/sulu` | Packagist | From 2.6.5 | 2.6.9 |
| `sulu/sulu` | Packagist | From 2.6.5 | 2.6.9 |
| `sulu/sulu` | Packagist | From 3.0.0-alpha1 | 3.0.0-alpha3 |
| `sulu/sulu` | Packagist | From 3.0.0-alpha1 | 3.0.0-alpha3 |

## How do I fix CVE-2025-47778?

Upgrade sulu/sulu to a fixed version for your release line: 2.5.25, 2.6.9 or 3.0.0-alpha3.

## Is CVE-2025-47778 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47778 and fix it if it is affected.

What it is: CVE-2025-47778 is a medium-severity vulnerability in sulu, published on 14 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47778 in the wild and no public exploit code.

Affected packages and fixed versions:
- sulu/sulu (Packagist): affected from 2.5.21; fixed in 2.5.25
- sulu/sulu (Packagist): affected from 2.5.21; fixed in 2.5.25
- sulu/sulu (Packagist): affected from 2.6.5; fixed in 2.6.9
- sulu/sulu (Packagist): affected from 2.6.5; fixed in 2.6.9
- sulu/sulu (Packagist): affected from 3.0.0-alpha1; fixed in 3.0.0-alpha3
- sulu/sulu (Packagist): affected from 3.0.0-alpha1; fixed in 3.0.0-alpha3

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

## Sources

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

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