Is CVE-2026-124470 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-124470 being exploited in the wild.

How severe is CVE-2026-124470?

Medium severity, with a CVSS score of 6.5, published 8 November 2026.

How is CVE-2026-124470 attacked?

It is attacked over the network.

Am I affected by CVE-2026-124470?

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.

CVE-2026-124470: OpenEMR broken object level authorization in patient portal report

CVE-2026-124470 · Severity: medium · CVSS 6.5 · Published 2026-11-08

OpenEMR is an electronic health record system used by healthcare organizations to store and manage patient medical data. An authenticated patient using the hospital's online portal can read confidential medical records—including diagnoses, clinical notes, and allergy information—belonging to any other patient in the system by manipulating report parameters. This allows unauthorized access to sensitive healthcare data without requiring special privileges.

Technologies: OpenEMR. Vendors: OpenEMR.

Quick answers

Is CVE-2026-124470 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-124470 being exploited in the wild.
How severe is CVE-2026-124470?: Medium severity, with a CVSS score of 6.5, published 8 November 2026.
Which products and versions are affected?: OpenEMR before 8.3.0.
Is there a fix for CVE-2026-124470?: Yes: fixed in 8.3.0. Until then: Restrict access to the patient portal to trusted users only, or disable the custom report functionality in portal/report/portal_custom_report.php if it is not actively used, until upgrading to the patched version. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-124470 attacked?: It is attacked over the network.
Am I affected by CVE-2026-124470?: 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

Restrict access to the patient portal to trusted users only, or disable the custom report functionality in portal/report/portal_custom_report.php if it is not actively used, until upgrading to the patched version.

Technical details

A broken object level authorization (BOLA) vulnerability in portal/report/portal_custom_report.php fails to validate that the requesting patient owns the problem list records they are querying. The code extracts a record ID from user-supplied issue_ parameters and queries the lists table without adding a patient ID condition, exposing fields (type, title, comments, diagnosis) for any record. An authenticated portal patient can enumerate sequential record IDs to retrieve all patients' problem lists and IPPF contraceptive records.

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.