Is ibexa/user 4.1 vulnerable?

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

Yes: 1 known advisory

Yes. ibexa/user 4.1.5, the last 4.1 release, is affected by 1 known security advisory (1 medium). Upgrade to 4.4.3 or later to fix all of them.

Upgrade with:composer require ibexa/user:^4.4.3

Is your project on an affected ibexa/user?

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

Advisories affecting ibexa/user 4.1.5

  • MediumGHSA-r3fg-3r88-6x3f10 May 2023

    Ibexa User Settings are accessible on the front-end for anonymous user

    Affected
    >=4.0.0 <4.4.3
    Fixed in
    4.4.3

Every ibexa/user 4.1.x release

Affected: 4.1.0 to 4.1.5. Latest ibexa/user: 5.0.11.

VersionKnown advisories
ibexa/user 4.1.5GHSA-r3fg-3r88-6x3f
ibexa/user 4.1.4GHSA-r3fg-3r88-6x3f
ibexa/user 4.1.3GHSA-r3fg-3r88-6x3f
ibexa/user 4.1.2GHSA-r3fg-3r88-6x3f
ibexa/user 4.1.1GHSA-r3fg-3r88-6x3f
ibexa/user 4.1.0GHSA-r3fg-3r88-6x3f

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

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ibexa/user version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other ibexa/user 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.