GHSA-8c2g-f8jm-5cr7: ibexa/fieldtype-richtext has an XSS vulnerability via acronym custom tag in Rich Text
Impact This security advisory resolves an XSS vulnerability in acronym custom tag in Rich Text, in the back office of the DXP. Back office access and varying levels of editing and management permissions are required to exploit this vulnerability. This typically means Editor or Administrator role, or similar.
Published Oct 17, 2025
Affected packages
ibexa/fieldtype-richtext
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.0.0, < 5.0.3
- Fixed in
- 5.0.3
- Check
composer show ibexa/fieldtype-richtext
ibexa/fieldtype-richtext
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.6.0, < 4.6.25
- Fixed in
- 4.6.25
- Check
composer show ibexa/fieldtype-richtext
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
This security advisory resolves an XSS vulnerability in acronym custom tag in Rich Text, in the back office of the DXP. Back office access and varying levels of editing and management permissions are required to exploit this vulnerability. This typically means Editor or Administrator role, or similar. Injected XSS is persistent and may in some cases be reflected in the front office, possibly affecting end users. The fixes ensure XSS is escaped, and any existing injected XSS is rendered harmless.
Patches
See "Patched versions".
Workarounds
None.
References
https://developers.ibexa.co/security-advisories/ibexa-sa-2025-004-xss-and-enumeration-vulnerabilities-in-back-office
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
