Read the docs

Insecure direct object reference in OpenEMR Carecoordination module

Priority LOW 37CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

OpenEMR before 8.5.0 contains an insecure direct object reference in its Carecoordination module, tracked as CWE-639. An authenticated remote user with the send_to_hie permission can supply arbitrary document or patient IDs to reach any patient's CCDA, CCR and QRDA documents. The attacker can download, transmit or export patient health records, inject falsified clinical data and delete audit records.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

OpenEMR before 8.5.0 contains an insecure direct object reference vulnerability in the Carecoordination module that allows authenticated users with send_to_hie permission to access any patient's CCDA/CCR/QRDA documents. Attackers can supply arbitrary document or patient IDs to download, transmit, or export patient health records, inject falsified clinical data, and delete audit records.

Why it matters now

EPSS 0.00303 23rd percentileScored 2026-11-16
Fix Fixed openemr (openemr): 8.5.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
openemropenemrbefore 8.5.08.5.0Patch availableCNA
  • openemr Vendoropenemr Affected before 8.5.0 Fixed in 8.5.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*——Open-Emr
  • cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* Versions — — ·Open-Emr

Remediation

Upgrade OpenEMR to version 8.5.0, which fixes this issue. The sources list no fixed version for other OpenEMR releases.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA openemr (openemr) Fixed in 8.5.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    openemr 8.5.0

    77 records Highest priority Priority HIGH 4 HIGH, 16 MEDIUM, 57 LOW

    Other records, highest priority first

    • TI-2026-91361 Missing authorization in OpenEMR custom export and chart-tracker scriptsPriority HIGH 73
    • TI-2026-91381 Second-order SQL injection in OpenEMR IPPF contraceptive issue featurePriority HIGH 72
    • TI-2026-91321 Unrestricted file upload in OpenEMR lets billing users execute PHPPriority HIGH 69

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-126470
  2. 2026-11-13 Alias added: GHSA-q3m7-vr7v-jgh4

References

  • TI-2026-91365 OpenEMR OAuth scope flaw exposes FHIR Patient records to attackers CVSS 4.0CRITICAL 9.3
  • TI-2026-86808 Token replay and PIN brute force in OpenEMR one-time authentication CVSS 4.0CRITICAL 9.3
  • TI-2026-24664 SQL Injection Vulnerability in ajax graphs library (OpenEMR) CVSS 3.1HIGH 8.8
  • TI-2026-85645 Missing access checks in OpenEMR let users reassign documents CVSS 3.1CRITICAL 9.6
  • TI-2026-28796 OpenEMR 8.2.0 Remote Code Execution via CategoryTree eval() Injection CVSS 4.0CRITICAL 9.4
  • TI-2026-20308 OpenEMR's payments gateway_api_key secret rendered into client JS code CVSS 3.1CRITICAL 9.6
See all 277 →

Sources