ezsystems/ezplatform-richtext allows access to external entities in XML

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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. We…

Published by the source

10 Apr 2025, 12:25 UTC

Last modified by the source

10 Apr 2025, 12:26 UTC

Source last checked

26 Oct 2026, 14:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2jqj-5qv2-xvcg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2jqj-5qv2-xvcg

Advisory: ezsystems/ezplatform-richtext allows access to external entities in XML
IDs: GHSA-2jqj-5qv2-xvcg
Record: https://patchnext.com/advisories/ghsa-2jqj-5qv2-xvcg (revision 1, source checked 26 Oct 2026, 14:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ezsystems/ezplatform-richtext 2.3.26. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ezsystems/ezplatform-richtext: affected >= 2.3.0-beta1, < 2.3.26; fixed in 2.3.26

## Suggested inspection (read-only)
- Packagist ezsystems/ezplatform-richtext: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ezsystems/ezplatform-richtext.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2jqj-5qv2-xvcg (GitHub-reviewed advisory GHSA-2jqj-5qv2-xvcg lists affected ranges: Packagist ezsystems/ezplatform-richtext >=2.3.0-beta1 <2.3.26)

Commands are suggestions: review each one before running it.