# CVE-2025-45731: Race condition in n/a

> A race condition in 2FAuth allows attackers to cause data inconsistencies and orphaned accounts during group deletion.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2025
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-ph6w-q992-7qrx, GHSA-vqm9-87vr-9765

## What is CVE-2025-45731?

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

### Official description

A group deletion race condition in 2FAuth v5.5.0 causes data inconsistencies and orphaned accounts when a group is deleted while other operations are pending.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: 2fauth 2fauth.

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

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

## Is CVE-2025-45731 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-32133](https://insights.sbomify.com/CVE-2026-32133/): 2FAuth has Blind SSRF in image parameter allows internal network access and more (high 7.8)
- [CVE-2024-52598](https://insights.sbomify.com/CVE-2024-52598/): 2FAuth vulnerable to Server Side Request Forgery + URI validation bypass in 2fauth /api/v1/twofaccounts/preview (high 7.5)
- [CVE-2024-52597](https://insights.sbomify.com/CVE-2024-52597/): 2FAuth vulnerable to stored cross-site scripting via SVG upload and direct access render (medium 6.1)
- [CVE-2023-36816](https://insights.sbomify.com/CVE-2023-36816/): Cross-Site Scripting (XSS) at Account creation in 2FAuth (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45731 is a medium-severity vulnerability in n/a, published on 24 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45731 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-45731/ (Markdown: https://insights.sbomify.com/CVE-2025-45731/index.md)
```

## Sources

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

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