Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to OpenEMR application
-
DeliveryAccess Patient Search endpoint
-
ExploitInject SQL payload in HTTP parameter keys
-
ExecutionExecute arbitrary SQL commands
-
ImpactExtract sensitive patient data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires authenticated user account in OpenEMR versions prior to 8.0.0.3. Attacker manipulates HTTP parameter keys in Patient Search functionality (/interface/new/new_search_popup.php) to inject SQL commands. No victim interaction needed beyond attacker possessing valid login credentials. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) indicates this is a network-exploitable vulnerability with low attack complexity requiring only low-level authentication, no user interaction, and delivering high confidentiality and integrity impact. While the 8.1 score suggests high severity, the PR:L requirement (authenticated access needed) reduces immediate internet-wide exploitation risk compared to unauthenticated vulnerabilities. The medical context significantly elevates real-world risk as OpenEMR handles HIPAA-protected patient health information, making data exfiltration particularly damaging from regulatory and privacy perspectives. A patch is available in version 8.0.0.3 with a specific commit reference, indicating the vendor has addressed the issue. Given OpenEMR's widespread use in healthcare settings, the availability of technical details in the GitHub Security Advisory (GHSA-2r7h-xm8v-m872), and the relative ease of exploitation once authenticated, this should be considered a high-priority remediation item for organizations running affected versions, particularly those in regulated healthcare environments. |
| Exploit ScenarioDerived | An attacker with valid low-privileged credentials to an OpenEMR installation accesses the Patient Search functionality at /interface/new/new_search_popup.php and crafts malicious HTTP requests where the parameter keys themselves contain SQL injection payloads rather than the parameter values. Using blind SQL injection techniques, the attacker iteratively extracts sensitive patient health information, user credentials, and other confidential database contents by observing application response timing or boolean conditions, eventually gaining access to the entire EHR database or escalating privileges to modify patient records. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
A Blind SQL Injection vulnerability exists in OpenEMR's Patient Search functionality that allows authenticated attackers to execute arbitrary SQL commands by manipulating HTTP parameter keys instead of values. OpenEMR versions prior to 8.0.0.3 are affected. With a CVSS score of 8.1 (High), this vulnerability enables high confidentiality and integrity impact, allowing attackers to extract sensitive patient health records and potentially modify database contents, though exploitation requires low-privileged authentication.
RemediationAI
Upgrade OpenEMR to version 8.0.0.3 or later, which contains a patch for this vulnerability as documented in commit c61887aa7c83e83b3282db05246f1c00de3aa21d available at https://github.com/openemr/openemr/commit/c61887aa7c83e83b3282db05246f1c00de3aa21d. Review the complete security advisory at https://github.com/openemr/openemr/security/advisories/GHSA-2r7h-xm8v-m872 for additional context. Until patching is completed, organizations should implement defense-in-depth measures including restricting access to the Patient Search functionality to only essential users, monitoring database query logs for anomalous SQL patterns, implementing web application firewall (WAF) rules to detect SQL injection attempts in parameter keys, and conducting audit reviews of user accounts with access to the affected functionality. Given the sensitive nature of healthcare data, prioritize this upgrade and ensure comprehensive logging is enabled to detect any potential exploitation attempts.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability affects OpenEMR, an open-source electronic health records (EHR) and medical practice management application written in PHP. The affected component is the Patient Search functionality located in /interface/new/new_search_popup.php. The vulnerability is classified as CWE-89 (SQL Injection) and represents a blind SQL injection attack where the attacker manipulates HTTP parameter keys rather than parameter values—an unusual attack vector that bypasses typical input validation focused on parameter values. The CPE identifier cpe:2.3:a:openemr:openemr:*:*:*:*:*:*:*:* confirms this affects the OpenEMR application across multiple versions. Blind SQL injection allows attackers to infer database content through boolean-based or time-based queries even when error messages are not displayed.
Know when Openemr gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
DescriptionGitHub Advisory
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, a Blind SQL Injection vulnerability exists in the Patient Search functionality (/interface/new/new_search_popup.php). The vulnerability allows an authenticated attacker to execute arbitrary SQL commands by manipulating the HTTP parameter keys rather than the values. Version 8.0.0.3 contains a patch.
Executive ViewAI
OpenEMR instances are vulnerable to SQL injection attacks that could expose protected health information (PHI) and patient records through the Patient Search feature. Any user with basic system access can exploit this vulnerability to extract or modify sensitive patient data, creating significant compliance and liability risks under HIPAA and state privacy regulations.
Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns in HTTP headers and parameter keys; disable or restrict access to Patient Search functionality until patched; enforce network segmentation to limit lateral movement from OpenEMR; require multi-factor authentication for all OpenEMR access; increase monitoring and alerting for database query anomalies; conduct regular audit logs review for suspicious database access patterns.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Affected Products (CPE)GitHub Advisory
An authenticated SQL injection vulnerability exists in OpenEMR ≤ 4.1.1 Patch 14 that allows a low-privileged attacker to
Unauthenticated token disclosure in OpenEMR before 8.0.0. CVSS 10.0. PoC and patch available.
Path traversal in OpenEMR 7.0.4 disposeDocument() allows file access. PoC available.
Path traversal in OpenEMR electronic health records before fix allows authenticated users to read arbitrary files on the
SQL injection in OpenEMR electronic health records before fix. Authenticated users can execute arbitrary SQL through the
OpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php, \controllers\C_Pharmacy.cl
An issue in OpenEMR 7.0.2 allows a remote attacker to escalate privileges viaa crafted POST request using the noteid par
Information disclosure in OpenEMR 5.0.2 to before 8.0.0 exposes sensitive data. PoC and patch available.
Remote code execution in OpenEMR through 8.2.0 lets an authenticated administrator poison the document category tree so
interface/fax/fax_dispatch.php in OpenEMR 4.1.0 allows remote authenticated users to execute arbitrary commands via shel
interface/globals.php in OpenEMR 2.x, 3.x, and 4.x before 4.2.0 patch 2 allows remote attackers to bypass authentication
Authentication bypass vulnerability in portal/account/register.php in versions of OpenEMR before 5.0.1.4 allows a remote
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB