# GHSA-q3x8-6898-23g3: ibexa/user login enumerates user accounts

> Attackers can enumerate valid user accounts via ambiguous login error messages in the Ibexa back-office.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2025

## What is GHSA-q3x8-6898-23g3?

GHSA-q3x8-6898-23g3 is a vulnerability in ibexa/user, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### 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

## Which versions are affected by GHSA-q3x8-6898-23g3?

2 open source packages ship an affected version, including ibexa/user.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibexa/user` | Packagist | From 5.0.0 | 5.0.3 |
| `ibexa/user` | Packagist | From 5.0.0 | 5.0.3 |

## How do I fix GHSA-q3x8-6898-23g3?

Upgrade ibexa/user to 5.0.3 or later.

## Is GHSA-q3x8-6898-23g3 being exploited?

There is no known exploitation of GHSA-q3x8-6898-23g3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q3x8-6898-23g3 and fix it if it is affected.

What it is: GHSA-q3x8-6898-23g3 is a vulnerability in ibexa/user, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-q3x8-6898-23g3 in the wild and no public exploit code.

Affected packages and fixed versions:
- ibexa/user (Packagist): affected from 5.0.0; fixed in 5.0.3
- ibexa/user (Packagist): affected from 5.0.0; fixed in 5.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-q3x8-6898-23g3/ (Markdown: https://insights.sbomify.com/GHSA-q3x8-6898-23g3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q3x8-6898-23g3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q3x8-6898-23g3/
Summaries are generated and may contain mistakes; the official description above is the record.