CVE-2026-126425
Awaiting Analysis Awaiting Analysis - Queue

Stored SQL Injection in OpenEMR Prior to 8.5.0

Publication date: 2026-11-13

Last updated on: 2026-11-13

Assigner: VulnCheck

Description
OpenEMR before 8.5.0 contains a stored SQL injection vulnerability in which History layout field identifiers saved through edit_layout.php, including HIS fields and LBF source-H fields, are placed unvalidated into an INSERT statement for patients without a history_data row. Users with admin/super and patients/med write access can trigger history_save.php or LBF saves to execute SQL functions like SLEEP, tying up database workers or accessing data beyond their privileges.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-13
Last Modified
2026-11-13
Generated
2026-11-13
AI Q&A
2026-11-13
EPSS Evaluated
N/A
NVD
CVE-2026-126425
EUVD
EUVD-2026-125018

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
openemr openemr to 8.5.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

OpenEMR before version 8.5.0 has a stored SQL injection flaw. It occurs when users with admin or patient write access save History layout fields via edit_layout.php. These fields are inserted unvalidated into an INSERT statement for patients without a history_data row. Attackers can exploit this to execute SQL functions like SLEEP, causing database delays or unauthorized data access.

Detection Guidance

To detect this vulnerability, inspect OpenEMR installations for versions before 8.5.0. Check for suspicious database activity like unusual SLEEP function calls or unauthorized data access attempts in logs. Review edit_layout.php and history_save.php for unvalidated History layout field inputs.

Impact Analysis

This vulnerability allows attackers with specific access levels to execute malicious SQL commands. This could lead to database performance degradation, unauthorized data access, or privilege escalation. Systems running vulnerable OpenEMR versions are at risk of data breaches or service disruptions.

Compliance Impact

This vulnerability could lead to unauthorized data access or breaches, violating GDPR's data protection principles or HIPAA's security requirements. Organizations using affected OpenEMR versions may face compliance violations, legal penalties, or reputational damage due to potential exposure of sensitive patient or user data.

Mitigation Strategies

Immediately upgrade OpenEMR to version 8.5.0 or later. Restrict write access for admin/super and patients/med roles to prevent exploitation. Monitor database queries for unexpected INSERT statements or SLEEP function usage.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-126425. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...