Summary
Ibexa RichText Field Type XSS vulnerabilities in back office
Workarounds
None.
Impact
This security advisory is a part of IBEXA-SA-2025-003, which resolves XSS vulnerabilities in several parts of the back office of Ibexa DXP. Back office access and varying levels of editing and management permissions are required to exploit these vulnerabilities. This typically means Editor or Administrator role, or similar. Injected XSS is persistent and can be reflected in the front office, possibly affecting end users. The fixes ensure XSS is escaped, and any existing injected XSS is rendered harmless.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- See "Patched versions".
- https://github.com/ibexa/fieldtype-richtext/commit/4a4a170c7faa4807ae0f74c581481b835bab3caf
Frequently Asked Questions
- What is GHSA-9QV6-4PWM-M68F? GHSA-9QV6-4PWM-M68F is a medium-severity cross-site scripting (XSS) vulnerability in ibexa/fieldtype-richtext (composer), affecting versions >= 4.6.0-beta1, < 4.6.21. It is fixed in 4.6.21. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of ibexa/fieldtype-richtext are affected by GHSA-9QV6-4PWM-M68F? ibexa/fieldtype-richtext (composer) versions >= 4.6.0-beta1, < 4.6.21 is affected.
- Is there a fix for GHSA-9QV6-4PWM-M68F? Yes. GHSA-9QV6-4PWM-M68F is fixed in 4.6.21. Upgrade to this version or later.
- Is GHSA-9QV6-4PWM-M68F exploitable, and should I be worried? Whether GHSA-9QV6-4PWM-M68F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-9QV6-4PWM-M68F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-9QV6-4PWM-M68F? Upgrade
ibexa/fieldtype-richtextto 4.6.21 or later.