# GHSA-2jqj-5qv2-xvcg: ezsystems/ezplatform-richtext allows access to external entities in XML

> An attacker with editor privileges can exploit XML external entity injection in RichText fields to read server files.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2025

## What is GHSA-2jqj-5qv2-xvcg?

GHSA-2jqj-5qv2-xvcg is a vulnerability in ezsystems/ezplatform-richtext, published on 10 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Impact
This security advisory resolves a vulnerability in the RichText field type. By entering a maliciously crafted input into the RichText XML, an attacker could perform an attack using XML external entity (XXE) injection, which might be able to read files on the server. To exploit this vulnerability the attacker would need to already have edit permission to content with RichText fields, which typically means Editor role or higher. The fix removes unsafe elements from XML code, while preserving safe elements.

If you have a stored XXE attack in your content drafts, the fix prevents it from extracting data both during editing and preview. However, if such an attack has already been published and the result is stored in the content, it is unfortunately not possible to detect and remove it by automatic means.

### Credits
This vulnerability was discovered and reported to Ibexa by Dennis Henke, Thorsten Niephaus, Marat Aytuganov, and Stephan Sekula of [Compass Security Deutschland GmbH](https://www.compass-security.com/en/). We thank them for reporting it responsibly to us.

### Patches
- See "Patched versions"
- https://github.com/ezsystems/ezplatform-richtext/commit/5ba2a82cc3aa6235ecfe87278e20c1451d9df913

### Workarounds
- Exploitation requires edit access to RichText content. If you can trust your editors, and you don't grant edit permission to any externals, you are not at risk in practice.

### References
- https://developers.ibexa.co/security-advisories/ibexa-sa-2025-002-xxe-vulnerability-in-richtext

## Which versions are affected by GHSA-2jqj-5qv2-xvcg?

2 open source packages ship an affected version, including ezsystems/ezplatform-richtext.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezplatform-richtext` | Packagist | From 2.3.0-beta1 | 2.3.26 |
| `ezsystems/ezplatform-richtext` | Packagist | From 2.3.0-beta1 | 2.3.26 |

## How do I fix GHSA-2jqj-5qv2-xvcg?

Upgrade ezsystems/ezplatform-richtext to 2.3.26 or later.

## Is GHSA-2jqj-5qv2-xvcg being exploited?

There is no known exploitation of GHSA-2jqj-5qv2-xvcg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2jqj-5qv2-xvcg and fix it if it is affected.

What it is: GHSA-2jqj-5qv2-xvcg is a vulnerability in ezsystems/ezplatform-richtext, published on 10 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2jqj-5qv2-xvcg in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezplatform-richtext (Packagist): affected from 2.3.0-beta1; fixed in 2.3.26
- ezsystems/ezplatform-richtext (Packagist): affected from 2.3.0-beta1; fixed in 2.3.26

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-2jqj-5qv2-xvcg/ (Markdown: https://insights.sbomify.com/GHSA-2jqj-5qv2-xvcg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2jqj-5qv2-xvcg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2jqj-5qv2-xvcg/
Summaries are generated and may contain mistakes; the official description above is the record.