CVE-2026-24898

OpenEMR has an Unauthenticated MedEx Token Disclosure

Published Mar 3, 2026 CVSS 3.1 · 10 Critical EPSS 2.4% KEV · Not listed
Description
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0, an unauthenticated token disclosure vulnerability in the MedEx callback endpoint allows any unauthenticated visitor to obtain the practice's MedEx API tokens, leading to complete third-party service compromise, PHI exfiltration, unauthorized actions on the MedEx platform, and HIPAA violations. The vulnerability exists because the endpoint bypasses authentication ($ignoreAuth = true) and performs a MedEx login whenever $_POST['callback_key'] is provided, returning the full JSON response including sensitive API tokens. This vulnerability is fixed in 8.0.0.

Analysis

AI-generated

Technical impact

The flaw allows any unauthenticated user to trigger a MedEx login via the callback endpoint by supplying a callback_key parameter, and because authentication is intentionally bypassed the resulting JSON response contains the full MedEx API token set. With these tokens an attacker can compromise the MedEx service, extract protected health information, and perform unauthorized actions, constituting a severe breach of HIPAA.

Affected Systems

Any installation of OpenEMR older than version 8.0.0 that exposes the MedEx callback endpoint is affected, including all OpenEMR instances listed under the openemr vendor in the CNA and CPE entries.

Risk and Exploitability

The vulnerability carries a CVSS base score of 10, the maximum severity, but its EPSS score of 2% indicates that exploitation is not currently widespread and the vulnerability is not listed in the CISA KEV catalog. The attack vector is unauthenticated and remote, requiring only a simple HTTP POST to the endpoint, making exploitation trivial if the application is reachable.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OpenEMR version 8.0.0 or later to eliminate the authentication bypass.
  • If an upgrade cannot be performed immediately, limit network access to the MedEx callback endpoint using firewall rules or IP whitelisting so that only authorized internal systems can reach it.
  • After remediation, rotate all MedEx API tokens and revoke any that may have been exposed to ensure that compromised credentials cannot be reused.

Generated by OpenCVE AI on October 29, 2026 at 23:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Open-emr
Open-emr openemr
CPEs cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*
Vendors & Products Open-emr
Open-emr openemr
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Openemr
Openemr openemr
Vendors & Products Openemr
Openemr openemr
Type Values Removed Values Added
Description OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.0.0, an unauthenticated token disclosure vulnerability in the MedEx callback endpoint allows any unauthenticated visitor to obtain the practice's MedEx API tokens, leading to complete third-party service compromise, PHI exfiltration, unauthorized actions on the MedEx platform, and HIPAA violations. The vulnerability exists because the endpoint bypasses authentication ($ignoreAuth = true) and performs a MedEx login whenever $_POST['callback_key'] is provided, returning the full JSON response including sensitive API tokens. This vulnerability is fixed in 8.0.0.
Title OpenEMR has an Unauthenticated MedEx Token Disclosure
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 10, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 4, 2026, 4:52 PM
Reserved
Jan 27, 2026, 7:35 PM
Status
Analyzed
Published
Mar 3, 2026, 10:16 PM
Modified
Jun 17, 2026, 10:23 AM