# CVE-2021-25923: Weak cryptography in openemr

> OpenEMR fails to enforce maximum password length, allowing attackers to bypass authentication using truncated passwords and take over accounts.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 24 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jgj9-5874-x5mv

## What is CVE-2021-25923?

CVE-2021-25923 is a high-severity vulnerability in Open-Emr Openemr, published on 24 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In OpenEMR, versions 5.0.0 to 6.0.0.1 are vulnerable to weak password requirements as it does not enforce a maximum password length limit. If a malicious user is aware of the first 72 characters of the victim user’s password, he can leverage it to an account takeover.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2021-25923?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2021-25923?

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

## Is CVE-2021-25923 being exploited?

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

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25923 and fix it if it is affected.

What it is: CVE-2021-25923 is a high-severity vulnerability in Open-Emr Openemr, published on 24 Jun 2021. 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-2021-25923 in the wild and no public exploit code.

Affected product: Open-Emr Openemr. 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-2021-25923/ (Markdown: https://insights.sbomify.com/CVE-2021-25923/index.md)
```

## Sources

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

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