Is ibexa/admin-ui vulnerable?

Composer ibexa/admin-ui has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

6advisories
2critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2024-53864Ibexa Admin UI vulnerable to Cross-site Scripting in a field that is used in the Content name patternmedium0.0>=4.6.0 and <4.6.144.6.14
CVE-2024-39318Ibexa Admin UI vulnerable to DOM-based Cross-site Scripting in file upload widgetmedium5.4>=4.6.0-beta1 and <4.6.94.6.9
GHSA-2mx6-fq24-g2mhibexa/admin-ui has an XSS vulnerability in Cancel/Reschedule future publication modalmedium0.0>=5.0.0 and <5.0.3 or >=4.6.0 and <4.6.255.0.3, 4.6.25
GHSA-5r6x-g6jv-4v87Ibexa Admin UI XSS vulnerabilities in back officemedium0.0>=4.6.0-beta1 and <4.6.214.6.21
GHSA-7644-cxp8-h23ribexa/admin-ui vulnerable to Cross-site Scripting in content type name/shortnamecritical0.0>=4.2.0 and <4.2.34.2.3
GHSA-g6jc-xrc3-4wwqIbexa DXP users with the Company admin role can assign any role to any usercritical0.0>=4.2.0 and <4.2.34.2.3

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.