GHSA-2jqj-5qv2-xvcg: Ezsystems/ezplatform richtext Ezsystems/ezplatform-richtext Allows Access To External Vulnerability

HIGH
Share
CWE-611
Published
Advisory Summary

GHSA-2jqj-5qv2-xvcg is a HIGH ezsystems/ezplatform-richtext allows access to external vulnerability (CWE-611: Improper Restriction of XML External Entity Reference) affecting Ezsystems/ezplatform richtext libraries in the Packagist ecosystem. The issue involves ezsystems/ezplatform-richtext allows access to external entities in xml. Remediation is available by upgrading affected packages to version 2.3.26.

GHSA-2jqj-5qv2-xvcg at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2jqj-5qv2-xvcg
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-611: Improper Restriction of XML External Entity Reference
Affected Product Ezsystems/ezplatform richtext
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-2jqj-5qv2-xvcg

To remediate this vulnerability, upgrade all affected Ezsystems/ezplatform richtext dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

ezsystems/ezplatform-richtext fixed: 2.3.26 
Upgrade ezsystems/ezplatform-richtext to 2.3.26
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for ezsystems/ezplatform-richtext

How to Check if You Are Affected

To determine whether your application is affected by GHSA-2jqj-5qv2-xvcg, inspect your project dependencies for Ezsystems/ezplatform richtext:

inspect dependencies for ezsystems/ezplatform-richtext

Analyze the terminal output to locate any version of Ezsystems/ezplatform richtext in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.26), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-611: Improper Restriction of XML External Entity Reference, where the product processes an xml document that can contain xml entities with uris that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. In Ezsystems/ezplatform richtext, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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

GHSA-2jqj-5qv2-xvcg Affected Ezsystems/ezplatform richtext Versions

1 component(s)
Fixed Versions:
2.3.26
Product / Package Ecosystem Affected Versions Fixed Version
ezsystems/ezplatform-richtext
 Packagist
≥ 2.3.0-beta1
< 2.3.26
2.3.26

References

GitHub Advisory / Wiki ADVISORY
https://github.com/ezsystems/ezplatform-richtext/security/advisories/GHSA-2jqj-5qv2-xvcg
Security Fix Commit FIX COMMIT
https://github.com/ezsystems/ezplatform-richtext/commit/5ba2a82cc3aa6235ecfe87278e20c1451d9df913
Ezsystems/ezplatform richtext Security Information SECURITY
https://developers.ibexa.co/security-advisories/ibexa-sa-2025-002-xxe-vulnerability-in-richtext
Ezsystems/ezplatform richtext Source Repository REPOSITORY
https://github.com/ezsystems/ezplatform-richtext

Frequently Asked Questions

What is GHSA-2jqj-5qv2-xvcg?
GHSA-2jqj-5qv2-xvcg is a security vulnerability in Ezsystems/ezplatform richtext involving ezsystems/ezplatform-richtext allows access to external entities in XML under CWE-611: Improper Restriction of XML External Entity Reference.
Which Ezsystems/ezplatform richtext versions are affected?
Affected versions include releases prior to 2.3.26 across affected packages: ezsystems/ezplatform-richtext.
What version fixes GHSA-2jqj-5qv2-xvcg?
Upgrading to 2.3.26 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ezsystems/ezplatform-richtext affected?
Yes, ezsystems/ezplatform-richtext is affected in releases prior to 2.3.26. Upgrade your dependency to 2.3.26 or later.
What CWE is associated with GHSA-2jqj-5qv2-xvcg?
GHSA-2jqj-5qv2-xvcg is classified under CWE-611: Improper Restriction of XML External Entity Reference (The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.).
How can I check Packagist dependencies for GHSA-2jqj-5qv2-xvcg?
Run the dependency tree command: 'inspect dependencies for ezsystems/ezplatform-richtext'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2jqj-5qv2-xvcg",
  "modified" : "2025-04-10T12:26:44Z",
  "published" : "2025-04-10T12:25:09Z",
  "aliases" : [ ],
  "summary" : "ezsystems/ezplatform-richtext allows access to external entities in XML",
  "details" : "### Impact\nThis 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.\n\nIf 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.\n\n### Credits\nThis 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.\n\n### Patches\n- See \"Patched versions\"\n- https://github.com/ezsystems/ezplatform-richtext/commit/5ba2a82cc3aa6235ecfe87278e20c1451d9df913\n\n### Workarounds\n- 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.\n\n### References\n- https://developers.ibexa.co/security-advisories/ibexa-sa-2025-002-xxe-vulnerability-in-richtext",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "ezsystems/ezplatform-richtext"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.3.0-beta1"
      }, {
        "fixed" : "2.3.26"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ezsystems/ezplatform-richtext/security/advisories/GHSA-2jqj-5qv2-xvcg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ezsystems/ezplatform-richtext/commit/5ba2a82cc3aa6235ecfe87278e20c1451d9df913"
  }, {
    "type" : "WEB",
    "url" : "https://developers.ibexa.co/security-advisories/ibexa-sa-2025-002-xxe-vulnerability-in-richtext"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ezsystems/ezplatform-richtext"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-611" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-04-10T12:25:09Z",
    "nvd_published_at" : null
  }
}