Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

ibexa/user login enumerates user accounts

GHSA-q3x8-6898-23g3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ibexa/user 5.0.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist ibexa/user

    Affected
    >= 5.0.0, < 5.0.3
    Fixed in
    5.0.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact In v5, error messages could provide enough information to tell whether a user exists or not. This is resolved by ensuring the error messages are sufficiently ambigious. Patches See "Patched versions". Workarounds None. Resources https://developers.ibexa.co/security-advisories/ibexa-sa-2025-004-xss-and-enumeration-vulnerabilities-in-back-office

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-q3x8-6898-23g3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-q3x8-6898-23g3

Advisory: ibexa/user login enumerates user accounts
IDs: GHSA-q3x8-6898-23g3
Record: https://patchnext.com/advisories/ghsa-q3x8-6898-23g3 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ibexa/user 5.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ibexa/user: affected >= 5.0.0, < 5.0.3; fixed in 5.0.3

## Suggested inspection (read-only)
- Packagist ibexa/user: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ibexa/user.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q3x8-6898-23g3 (GitHub-reviewed advisory GHSA-q3x8-6898-23g3 lists affected ranges: Packagist ibexa/user >=5.0.0 <5.0.3)

Commands are suggestions: review each one before running it.

Loading voting…