# CVE-2025-32967: OpenEMR doesn't log password administration properly

> OpenEMR fails to log password change events, preventing administrators from auditing critical actions and enabling undetectable misuse.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-7qj6-jxfc-xw4v

## What is CVE-2025-32967?

CVE-2025-32967 is a medium-severity vulnerability in Open-Emr Openemr, published on 23 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenEMR is a free and open source electronic health records and medical practice management application. A logging oversight in versions prior to 7.0.3.4 allows password change events to go unrecorded on the client-side log viewer, preventing administrators from auditing critical actions. This weakens traceability and opens the system to undetectable misuse by insiders or attackers. Version 7.0.3.4 contains a patch for the issue.

Weakness: CWE-778 (Insufficient Logging)

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

It affects 1 product.


Products: Open-Emr Openemr.

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

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

## Is CVE-2025-32967 being exploited?

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

## 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-2025-32967 and fix it if it is affected.

What it is: CVE-2025-32967 is a medium-severity vulnerability in Open-Emr Openemr, published on 23 May 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-32967 exists.

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-2025-32967/ (Markdown: https://insights.sbomify.com/CVE-2025-32967/index.md)
```

## Sources

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

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