CVE-2026-126480
Awaiting Analysis Awaiting Analysis - Queue

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 an sql injection vulnerability in CcrTable::insertApprovedData() that allows authenticated users to inject SQL through request parameter names used as column names. Attackers can send crafted patient_data-*-sel parameters to the revandapprove route, lacking ACL and CSRF checks, to copy password hashes into patient fields or corrupt records.

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-126480
EUVD
EUVD-2026-124944

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 versions before 8.5.0 have an SQL injection flaw in the CcrTable::insertApprovedData() function. Authenticated users can exploit this by sending crafted parameters named patient_data-*-sel to the revandapprove route. The vulnerability exists because the application does not validate these parameters properly, allowing attackers to inject malicious SQL code.

Detection Guidance

Check OpenEMR version for versions before 8.5.0. Monitor network traffic for unusual SQL-like parameter patterns in requests to the revandapprove route, specifically looking for patient_data-*-sel parameters.

Impact Analysis

This vulnerability allows attackers to execute arbitrary SQL commands on the database. They could steal sensitive data like password hashes, modify or delete patient records, or corrupt the entire database. Since it requires authentication, attackers must first gain access to a valid user account.

Compliance Impact

This vulnerability could lead to unauthorized access to protected health information (PHI), violating HIPAA requirements for confidentiality and integrity. It may also result in GDPR non-compliance due to unauthorized data access or breaches of personal data security.

Mitigation Strategies

Upgrade OpenEMR to version 8.5.0 or later immediately. Apply input validation to sanitize request parameters. Implement ACL and CSRF checks for the revandapprove route. Review database for unauthorized modifications.

Chat Assistant

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