# CVE-2025-23214: Cosmos userbase checking vulnerability

> Attackers can enumerate valid usernames by analyzing login error codes, exposing user existence in the database.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-5843-2p4f-57fh

## What is CVE-2025-23214?

CVE-2025-23214 is a medium-severity vulnerability in azukaar Cosmos-Server, published on 20 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cosmos provides users the ability self-host a home server by acting as a secure gateway to your application, as well as a server manager. By monitoring the error code returned in the login, it is possible to figure out whether a user exist or not in the database. Patched in 0.17.7.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

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

## Is CVE-2025-23214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23214 is a medium-severity vulnerability in azukaar Cosmos-Server, published on 20 Jan 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-23214 in the wild and no public exploit code.

Affected product: azukaar Cosmos-Server. 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-23214/ (Markdown: https://insights.sbomify.com/CVE-2025-23214/index.md)
```

## Sources

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

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