Is ibexa/core 4.2 vulnerable?
Composer · 5 releases from 4.2.0 to 4.2.4 · latest ibexa/core is 5.0.11 · checked 18 Nov 2026
No known advisories in the last release
ibexa/core 4.2.4, the last 4.2 release, has no known advisories. 1 advisory affects earlier 4.2.x releases, so update to 4.2.4.
composer require ibexa/core:^4.2.4Is your project on an affected ibexa/core?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.2.x, affecting earlier releases
Ibexa DXP users with the Company admin role can assign any role to any user
- Affected
- >=4.2.0 <4.2.3
- Fixed in
- 4.2.3
Every ibexa/core 4.2.x release
Affected: 4.2.0 to 4.2.2. 4.2.3 and later are not affected. Latest ibexa/core: 5.0.11.
| Version | Known advisories |
|---|---|
| ibexa/core 4.2.4 | None |
| ibexa/core 4.2.3 | None |
| ibexa/core 4.2.2 | GHSA-394j-x37r-2q27 |
| ibexa/core 4.2.1 | GHSA-394j-x37r-2q27 |
| ibexa/core 4.2.0 | GHSA-394j-x37r-2q27 |
Which of your client projects are still on ibexa/core 4.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ibexa/core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other ibexa/core versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.