Skip to content
Threat Feed
high advisory

OpenEMR SQL Injection Vulnerability (CVE-2026-33910)

OpenEMR versions up to 8.0.0.2 are vulnerable to SQL injection in the patient selection feature, which can be exploited by authenticated attackers due to insufficient input validation, potentially leading to unauthorized data access and modification.

CVE search metadata

CVE search record: CVE-2026-33910. KEV: no. Product: OpenEMR (< 8.0.0.3). Brief: OpenEMR SQL Injection Vulnerability (CVE-2026-33910). Brief link: https://feed.craftedsignal.io/briefs/2026-03-openemr-sqli/

Triage facts

Revision 1
Applicability
OpenEMR (< 8.0.0.3)
Evidence
Unknown
Severity
High
Sources
5 public sources
Freshness
Revision 1Mar 26, 12:00 UTC
Detection
2 rules
Vulnerabilities
1 CVE

What's new

  • 1. new product Oct 16, 00:05 via sploitus

OpenEMR, a widely-used open-source electronic health records and medical practice management application, is vulnerable to SQL injection. Specifically, versions up to and including 8.0.0.2 contain a flaw in the patient selection feature (CVE-2026-33910). Authenticated attackers with valid user credentials can exploit this vulnerability due to insufficient input validation. Successful exploitation allows attackers to execute arbitrary SQL queries, potentially leading to unauthorized access, modification, or deletion of sensitive patient data. OpenEMR version 8.0.0.3 addresses this vulnerability with a patch. This vulnerability poses a significant risk to healthcare providers and their patients, potentially leading to data breaches, compliance violations, and reputational damage.

Attack Chain

  1. An attacker gains valid credentials for an OpenEMR user account.
  2. The attacker logs into the OpenEMR application.
  3. The attacker navigates to the patient selection feature within the application.
  4. The attacker crafts a malicious SQL query and injects it into the input fields of the patient selection form.
  5. The application executes the attacker-controlled SQL query against the database.
  6. The attacker retrieves sensitive patient data, such as personal information, medical history, and insurance details.
  7. The attacker modifies patient records, potentially altering medical diagnoses or treatment plans.
  8. The attacker exfiltrates the stolen data or uses it for malicious purposes, like identity theft or fraud.

Impact

Successful exploitation of this SQL injection vulnerability (CVE-2026-33910) could result in a significant data breach, potentially affecting thousands of patients. The healthcare sector is a prime target for cyberattacks due to the sensitive nature of the data it holds. A successful attack could lead to regulatory fines, legal action, and a loss of trust from patients and the community. The impact includes unauthorized access to Electronic Health Records (EHR), potential modification of medical information, and exfiltration of Protected Health Information (PHI).

Recommendation

  • Immediately upgrade all OpenEMR installations to version 8.0.0.3 or later to patch the SQL injection vulnerability (CVE-2026-33910).
  • Deploy the Sigma rules provided in this brief to detect potential exploitation attempts against the patient selection feature.
  • Implement input validation and sanitization measures for all user-supplied data within the OpenEMR application to prevent future SQL injection vulnerabilities.
  • Review and enforce strong authentication and authorization policies for all OpenEMR user accounts.

Detection coverage 2

Detect SQL Injection Attempts in OpenEMR Patient Selection

high

Detects potential SQL injection attempts in OpenEMR patient selection based on suspicious characters and keywords in HTTP requests.

sigma tactics: initial_access techniques: T1190, T1505 sources: webserver, linux

Detect OpenEMR SQL Injection via POST Request

high

Detects SQL injection attempts targeting OpenEMR by analyzing POST request data for common SQL injection payloads.

sigma tactics: initial_access techniques: T1190, T1505 sources: webserver, linux

Detection queries are available on the platform. Get full rules →