LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23627: OpenEMR has SQL Injection in Immunization Search/Report

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, an SQL injection vulnerability in the Immunization module allows any authenticated user to execute arbitrary SQL queries, leading to complete database compromise, PHI exfiltration, credential theft, and potential remote code execution. The vulnerability exists because user-supplied `patient_id` values are directly concatenated into SQL WHERE clauses without parameterization or escaping. Version 8.0.0 patches the issue.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenEMR before 8.0.0 has a serious SQL injection flaw in the Immunization search/report area. Any authenticated user could potentially compromise the full database, including protected health information and credentials. For healthcare environments, this is a high-priority privacy and operational risk.

Executive priority

Treat as urgent for any healthcare or clinical system using OpenEMR. The issue can affect PHI confidentiality and database integrity, but it requires authentication. Prioritize upgrade, access review, and compromise assessment for exposed or shared-user environments.

Technical view

CVE-2026-23627 is a CWE-89 SQL injection in OpenEMR’s Immunization module. User-supplied patient_id values are concatenated into SQL WHERE clauses without parameterization or escaping. The advisory states this can allow arbitrary SQL queries, complete database compromise, PHI exfiltration, credential theft, and potential remote code execution. Fixed in OpenEMR 8.0.0.

Likely exposure

Organizations running OpenEMR versions earlier than 8.0.0 are affected. Exposure requires an authenticated user account, but the source states any authenticated user can trigger the vulnerable path. Risk is greater where OpenEMR is broadly accessible or accounts are weakly controlled.

Exploitation context

The CVSS 4.0 score is 7.4 with network attack vector, low complexity, low privileges, and no user interaction. The provided sources do not state active exploitation, and this CVE is not listed as KEV in the supplied data.

Researcher notes

Evidence is from the CVE record, GitHub Security Advisory, and linked fix commit. The root cause is unsafe patient_id handling in SQL construction. Do not assume unauthenticated exploitation or active exploitation from the provided sources.

Mitigation direction

  • Upgrade OpenEMR to version 8.0.0 or later.
  • Review the GitHub advisory for vendor-specific remediation details.
  • Limit OpenEMR access to trusted users until upgraded.
  • Review account security and disable unnecessary authenticated accounts.
  • Assess whether PHI or credentials may have been exposed.

Validation and detection

  • Inventory all OpenEMR deployments and record versions.
  • Confirm no production instance runs below OpenEMR 8.0.0.
  • Verify the Immunization module is no longer using the vulnerable release.
  • Review database and application logs for unusual Immunization search activity.
  • Confirm remediation against the vendor advisory and patch reference.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23627 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.4High
CVSS 4.0 vector shape for CVE-2026-23627Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
openemropenemr< 8.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.