Is ibexa/core 4.1 vulnerable?

Composer · 6 releases from 4.1.0 to 4.1.5 · latest ibexa/core is 5.0.11 · checked 18 Nov 2026

No known advisories in the last release

ibexa/core 4.1.5, the last 4.1 release, has no known advisories. 2 advisories affect earlier 4.1.x releases, so update to 4.1.5.

Update within 4.1:composer require ibexa/core:^4.1.5

Is your project on an affected ibexa/core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.1.x, affecting earlier releases

  • CriticalGHSA-2x4v-g8cx-jxrq2 Jun 2022

    Login timing attack in ibexa/core

    Affected
    >=4.0.0 <4.0.7 · >=4.1.0 <4.1.4
    Fixed in
    4.0.7, 4.1.4
  • CriticalGHSA-gvj8-4cj4-h77629 Apr 2022

    Object state limitation has no effect

    Affected
    >=4.0.0 <4.0.5 · >=4.1.0 <4.1.2
    Fixed in
    4.0.5, 4.1.2

Every ibexa/core 4.1.x release

Affected: 4.1.0 to 4.1.3. 4.1.4 and later are not affected. Latest ibexa/core: 5.0.11.

VersionKnown advisories
ibexa/core 4.1.5None
ibexa/core 4.1.4None
ibexa/core 4.1.3GHSA-2x4v-g8cx-jxrq
ibexa/core 4.1.2GHSA-2x4v-g8cx-jxrq
ibexa/core 4.1.1GHSA-2x4v-g8cx-jxrq, GHSA-gvj8-4cj4-h776
ibexa/core 4.1.0GHSA-2x4v-g8cx-jxrq, GHSA-gvj8-4cj4-h776

Which of your client projects are still on ibexa/core 4.1?

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.