CVE-2026-126491
Awaiting Analysis Awaiting Analysis - Queue

Stored SQL Injection in OpenEMR Before 8.5.0

Vulnerability report for CVE-2026-126491, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

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 getByPatientDemographics() where layout_options field_id values are concatenated into the patient search WHERE clause. Attackers with Layout Editor access can plant a malicious field_id, allowing any authenticated low-privilege user to exfiltrate data from patient_data and users_secure tables.

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
EUVD

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 in the getByPatientDemographics() function. Attackers with Layout Editor access can insert malicious field_id values into the layout_options table. These values are then used in a patient search query without proper sanitization, allowing SQL commands to be injected. This lets any authenticated low-privilege user steal data from patient_data and users_secure tables.

Detection Guidance

Check OpenEMR version with: grep -r "version" /var/www/html/openemr/library/sql.inc.php. If version is below 8.5.0, the system is vulnerable. Review patient.inc.php for getByPatientDemographics() function usage. Look for layout_options table access by non-admin users.

Impact Analysis

If exploited, attackers can access sensitive patient information such as medical records and user credentials. The attack requires only Layout Editor access to plant the exploit and any authenticated user to trigger it. This could lead to data breaches, identity theft, or unauthorized access to confidential health information.

Compliance Impact

This vulnerability likely violates HIPAA due to unauthorized access to protected health information. It may also breach GDPR if EU patient data is exposed, leading to legal penalties, fines, and reputational damage for organizations handling such data.

Mitigation Strategies

Upgrade OpenEMR to version 8.5.0 or later immediately. Restrict Layout Editor access to trusted administrators only. Review and sanitize all field_id inputs in layout_options table. Monitor database queries for suspicious patterns or unauthorized data access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-126491. 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...