# CVE-2025-50594: Auth bypass in n/a

> Attackers can reset any account password in the Danphe Health Hospital Management System EMR, leading to unauthorized account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2025
- **Updated:** 14 Aug 2025
- **Also known as:** GHSA-327m-fmgh-c794

## What is CVE-2025-50594?

CVE-2025-50594 is a critical authentication bypass vulnerability in n/a, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in /Code/Websites/DanpheEMR/Controllers/Settings/SecuritySettingsController.cs in Danphe Health Hospital Management System EMR 3.2 allowing attackers to reset any account password.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2025-50594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50594 is a critical authentication bypass vulnerability in n/a, published on 13 Aug 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-50594 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-50594/ (Markdown: https://insights.sbomify.com/CVE-2025-50594/index.md)
```

## Sources

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

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