How severe is GHSA-cj3w-g42v-wcj6?

No CVSS score has been assigned to GHSA-cj3w-g42v-wcj6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cj3w-g42v-wcj6?

GHSA-cj3w-g42v-wcj6 affects the following packages: ibexa/fieldtype-richtext (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cj3w-g42v-wcj6?

Update ibexa/fieldtype-richtext to 4.6.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj3w-g42v-wcj6 is resolved across your whole dependency graph.

How do I detect GHSA-cj3w-g42v-wcj6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/fieldtype-richtext, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cj3w-g42v-wcj6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-cj3w-g42v-wcj6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cj3w-g42v-wcj6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-cj3w-g42v-wcj6 published, and has it been updated?

GHSA-cj3w-g42v-wcj6 was published on April 10, 2025 and was last updated on April 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

ibexa/fieldtype-richtext allows access to external entities in XMLGHSA-cj3w-g42v-wcj6

Fix: ibexa/fieldtype-richtext@823cba6

GHSA-cj3w-g42v-wcj6 is a security vulnerability in ibexa/fieldtype-richtext. A fix is available for ibexa/fieldtype-richtext — see the affected versions and patch details below.

Published

Apr 10, 2025

Updated

Apr 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 10, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ibexa/fieldtype-richtext

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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. We thank them for reporting it responsibly to us.

Patches

See "Patched versions"
https://github.com/ibexa/fieldtype-richtext/commit/823cba6b5ee2e81d7d74e622ce42c1451e8e1337

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/fieldtype-richtext`	≥ 4.6.0-beta1&&< 4.6.19	4.6.19`composer require ibexa/fieldtype-richtext:^4.6.19`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/fieldtype-richtext, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/fieldtype-richtext to 4.6.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj3w-g42v-wcj6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-cj3w-g42v-wcj6 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works