Read the docs

Insecure direct object reference in OpenEMR lets patients forge billing records

Priority MEDIUM 64CWE-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
None · High · None
Fix status
Fixed

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

Summary

OpenEMR before 8.3.0 contains an insecure direct object reference in portal/lib/paylib.php. The code writes the request-supplied form_pid value to onsite_portal_activity without checking it against the logged-in patient, which is CWE-639. An authenticated portal patient can insert or modify forged payment-audit records in other patients' billing records.

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

Description from the CNA

OpenEMR before 8.3.0 contains an insecure direct object reference in portal/lib/paylib.php, which writes the request-supplied form_pid (or the patient_id_cc value in Sphere data) to onsite_portal_activity without checking it against the session patient. Authenticated portal patients can submit portal-save, review-save, AuthorizeNet, Stripe, or Sphere requests to insert or modify forged payment-audit records in other patients' billing records.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00181 7th percentileScored 2026-11-16
Fix Fixed openemr (openemr): 8.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
openemropenemrbefore 8.3.08.3.0Patch availableCNA
  • openemr Vendoropenemr Affected before 8.3.0 Fixed in 8.3.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.3.0, which fixes this flaw.

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

  • Fix · CNA openemr (openemr) Fixed in 8.3.0

Fixed in the same release

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

  • Release ·

    openemr 8.3.0

    29 records Highest priority Priority HIGH 11 HIGH, 12 MEDIUM, 6 LOW

    Other records, highest priority first

    • TI-2026-86825 Stored cross-site scripting in OpenEMR CAMOS Rx print viewPriority HIGH 75
    • TI-2026-86813 Path traversal in OpenEMR lets users read and write arbitrary filesPriority HIGH 75
    • TI-2026-86837 Missing authorization in OpenEMR lets users delete recall recordsPriority HIGH 73

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-124476
  2. 2026-11-08 Alias added: GHSA-m965-q963-p5wc
  3. 2026-11-10 Priority changed: MEDIUM → LOW
  4. 2026-11-13 CISA SSVC decision points changed

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