CVE-2026-126489
Awaiting Analysis Awaiting Analysis - Queue

OpenEMR Second-Order SQL Injection in IPPF Contraceptive Issue Feature

Vulnerability report for CVE-2026-126489, 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 second-order SQL injection vulnerability in the IPPF contraceptive issue feature because issue_ippf_con_save concatenates layout_options field_id values into a REPLACE INTO query as column names. Authenticated administrators can add a malicious field_id via edit_layout.php, then trigger issue_ippf_con_save through add_edit_issue.php to execute arbitrary SQL.

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

This is a second-order SQL injection vulnerability in OpenEMR versions before 8.5.0. It exists in the IPPF contraceptive issue feature where the issue_ippf_con_save function concatenates layout_options field_id values directly into a REPLACE INTO query as column names without proper sanitization. Authenticated administrators can exploit this by inserting malicious field_id values via edit_layout.php and triggering the vulnerable code through add_edit_issue.php to execute arbitrary SQL commands.

Detection Guidance

To detect this vulnerability, inspect OpenEMR versions prior to 8.5.0 for the IPPF contraceptive issue feature. Check for unauthorized modifications in the layout_options table via edit_layout.php and trace SQL queries involving issue_ippf_con_save in add_edit_issue.php. Look for suspicious field_id values in database logs.

Impact Analysis

An attacker with administrative access could exploit this to execute arbitrary SQL queries, leading to unauthorized database access, data breaches of sensitive medical information, server-side code execution, and full database compromise. The impact includes potential theft or manipulation of patient records, system takeover, and disruption of healthcare services.

Compliance Impact

This vulnerability could severely impact compliance with GDPR and HIPAA by enabling unauthorized access to protected health information (PHI). GDPR requires strict data protection and breach notification, while HIPAA mandates safeguards for electronic protected health information (ePHI). A successful exploit could result in regulatory penalties, legal liabilities, and loss of patient trust due to compromised sensitive data.

Mitigation Strategies

Immediately upgrade OpenEMR to version 8.5.0 or later. If upgrading is not possible, restrict administrative access to edit_layout.php and add_edit_issue.php. Review database logs for signs of exploitation and remove any unauthorized field_id entries in the layout_options table.

Chat Assistant

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