# CVE-2025-55795: Business logic in n/a

> An attacker can lock out other users by stealing their email addresses due to flawed verification logic in the OpenML web application.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-87c5-mc8v-xf7r

## What is CVE-2025-55795?

CVE-2025-55795 is a low-severity vulnerability in n/a, published on 29 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The openml/openml.org web application version v2.0.20241110 uses incremental user IDs and insufficient email ownership verification during email update workflows. An authenticated attacker controlling a user account with a lower user ID can update their email address to that of another user with a higher user ID without proper verification. This results in the victim's email being reassigned to the attacker's account, causing the victim to be locked out immediately and unable to log in. The vulnerability leads to denial of service via account lockout but does not grant the attacker direct access to the victim's private data.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Openml Openml Frontend.

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

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

## Is CVE-2025-55795 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55795 exists.

## Other vulnerabilities in n/a

- [CVE-2025-55796](https://insights.sbomify.com/CVE-2025-55796/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55795 is a low-severity vulnerability in n/a, published on 29 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55795 exists.

Affected product: n/a. 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-55795/ (Markdown: https://insights.sbomify.com/CVE-2025-55795/index.md)
```

## Sources

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

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