# CVE-2025-24391: Possible user enumeration

> Attackers can enumerate valid user accounts via HTTP response differences in the OTRS External Interface, exposing user email addresses.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-fhjw-qvv3-45m7

## What is CVE-2025-24391?

CVE-2025-24391 is a medium-severity vulnerability in OTRS, published on 14 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the External Interface of OTRS allows conclusions to be drawn about the existence of user accounts through different HTTP response codes and messages. This enables an attacker to systematically identify valid email addresses.

This issue affects: 

  *  OTRS 7.0.X

  *  OTRS 8.0.X
  *  OTRS 2023.X
  *  OTRS 2024.X
  *  OTRS 2025.X

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2025-24391?


## How do I fix CVE-2025-24391?

No fix has been published for CVE-2025-24391 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24391 being exploited?

There is no known exploitation of CVE-2025-24391 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24391 and fix it if it is affected.

What it is: CVE-2025-24391 is a medium-severity vulnerability in OTRS, published on 14 Jul 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 CVE-2025-24391 in the wild and no public exploit code.

Affected product: OTRS. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2025-24391/ (Markdown: https://insights.sbomify.com/CVE-2025-24391/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24391
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24391
- OSV: https://osv.dev/vulnerability/CVE-2025-24391

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24391/
Summaries are generated and may contain mistakes; the official description above is the record.