CVE-2025-67752 OpenEMR Has Disabled SSL Certificate Verification in HTTP Client
OpenEMR disables SSL verification by default, allowing man-in-the-middle attacks to intercept sensitive healthcare data during external HTTPS communications.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-67752?
CVE-2025-67752 is a high-severity vulnerability in Open-Emr Openemr, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 7.0.4, OpenEMR's HTTP client wrapper (`oeHttp`/`oeHttpRequest`) disables SSL/TLS certificate verification by default (`verify: false`), making all external HTTPS connections vulnerable to man-in-the-middle (MITM) attacks. This affects communication with government healthcare APIs and user-configurable external services, potentially exposing Protected Health Information (PHI). Version 7.0.4 fixes the issue.
Weakness: CWE-295
Which versions are affected by CVE-2025-67752?
It affects 1 product.
Products include Open-Emr Openemr.
How do I fix CVE-2025-67752?
No fix has been published for CVE-2025-67752 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-67752 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67752 exists.
Other vulnerabilities in Open-Emr Openemr
- CVE-2026-24898 OpenEMR has an Unauthenticated MedEx Token Disclosure
- CVE-2026-24849 OpenEMR Arbitrary File Read Vulnerability
- CVE-2026-24908 OpenEMR has SQL Injection in Patient API Sort Parameter
- CVE-2022-2734 Improper Restriction of Rendered UI Layers or Frames in openemr/openemr
- CVE-2024-22611 SQL injection in n/a
Sources
Also known as GHSA-2g6h-725p-pqhp.