CVE-2026-124488: OpenEMR authorization bypass in encounter form loaders

CVE-2026-124488 · Severity: high · CVSS 8.1 · Published 2026-11-08

OpenEMR is a medical records system used by healthcare providers to manage patient information and clinical notes. An authenticated clinician without permission to access high-sensitivity patient encounters can bypass access controls to read and modify restricted clinical notes and care plans, compromising the confidentiality and integrity of sensitive medical records. This affects clinicians who should be blocked from viewing certain patients' information but can still tamper with those records through direct form submission.

Technologies: OpenEMR. Vendors: OpenEMR.

Quick answers

Is CVE-2026-124488 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-124488 being exploited in the wild.
How severe is CVE-2026-124488?
High severity, with a CVSS score of 8.1, published 8 November 2026.
Which products and versions are affected?
OpenEMR before 8.3.0.
Is there a fix for CVE-2026-124488?
Yes: fixed in 8.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-124488 attacked?
It is attacked over the network.
Am I affected by CVE-2026-124488?
Check whether you run OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 8.3.0

Technical details

An authenticated authorization bypass in OpenEMR's load_form.php and form save handlers (clinical_notes/save.php, care_plan/save.php) fails to enforce encounter sensitivity checks that are correctly enforced in the normal encounter UI. An attacker with clinician-level access but lacking the sensitivities|high permission can directly request high-sensitivity form loaders, obtain form content and valid CSRF tokens, and submit those forms to modify restricted records. The vulnerability requires valid OpenEMR credentials and knowledge of a high-sensitivity encounter.

Affected products

  • OpenEMR OpenEMR before 8.3.0

Timeline

  • 2026-08-18: disclosed
  • 2026-11-08: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.