Read the docs

SQL injection in OpenEMR CCR revandapprove field names

Priority LOW 37CWE-89Published · Updated

Key facts

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

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

Summary

OpenEMR before 8.5.0 contains an SQL injection flaw in the CCR revandapprove controller. An authenticated user with core access can supply crafted patient_data field names that are placed into an UPDATE statement, which is a case of improper neutralization of special elements in SQL commands (CWE-89). An attacker can use this to read staff password hashes and patient portal reset values, alter arbitrary patient demographics, and take over patient portal accounts.

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

Description from the CNA

OpenEMR before 8.5.0 contains an sql injection vulnerability that allows any authenticated core user to inject SQL by supplying crafted patient_data field names to the CCR revandapprove controller. Attackers can embed scalar subqueries in the UPDATE patient_data SET clause to read staff password hashes and portal reset values, alter arbitrary patient demographics, and take over patient-portal accounts.

Why it matters now

EPSS 0.00354 29th 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 or later, which fixes the issue.

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-126430
  2. 2026-11-13 Alias added: GHSA-54mg-j2w3-j7fj

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