Is ibexa/core vulnerable?

Composer ibexa/core has 5 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

5advisories
3critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
GHSA-2x4v-g8cx-jxrqLogin timing attack in ibexa/corecritical0.0>=4.0.0 and <4.0.7 or >=4.1.0 and <4.1.44.0.7, 4.1.4
GHSA-394j-x37r-2q27Ibexa DXP users with the Company admin role can assign any role to any usercritical0.0>=4.2.0 and <4.2.34.2.3
GHSA-9j39-4686-m3c4Ibexa Kernel's files with blacklisted extensions can be still saved to draftsmedium0.0>=4.5.0 and <4.5.6 or >=4.6.0 and <4.6.24.5.6, 4.6.2
GHSA-g95c-xc83-8353Ibexa DXP Download route allows filename changelow0.0>=4.5.0 and <4.5.44.5.4
GHSA-gvj8-4cj4-h776Object state limitation has no effectcritical0.0>=4.0.0 and <4.0.5 or >=4.1.0 and <4.1.24.0.5, 4.1.2

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.