Ibexa eZ Platform Admin UI assets XSS vulnerabilities in back officeGHSA-r5rx-53g9-25rj
Fix: ezsystems/ezplatform-admin-ui-assets@219b71bGHSA-r5rx-53g9-25rj is a security vulnerability in ezsystems/ezplatform-admin-ui-assets. A fix is available for ezsystems/ezplatform-admin-ui-assets — see the affected versions and patch details below.
Real-World Exposure
ezsystems/ezplatform-admin-ui-assetsReal-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 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.
Patches
- See "Patched versions".
- https://github.com/ezsystems/ezplatform-admin-ui-assets/commit/219b71b70aaea9321947d2dbeb49fff1b49e05f4
Workarounds
None.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezplatform-admin-ui-assets | ≥ 5.3.0-beta1&&< 5.3.5 | 5.3.5composer require ezsystems/ezplatform-admin-ui-assets:^5.3.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-admin-ui-assets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform-admin-ui-assets to 5.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5rx-53g9-25rj is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-r5rx-53g9-25rj in your dependencies?
Find it across Packagist, including transitive dependencies.