LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25746: OpenEMR has SQL Injection Vulnerability

OpenEMR is a free and open source electronic health records and medical practice management application. Versions prior to 8.0.0 contain a SQL injection vulnerability in prescription that can be exploited by authenticated attackers. The vulnerability exists due to insufficient input validation in the prescription listing functionality. Version 8.0.0 fixes the vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenEMR versions before 8.0.0 have a high-severity SQL injection flaw in prescription listing. An authenticated user could potentially access, alter, or disrupt database-backed medical records. Healthcare environments running older OpenEMR should prioritize upgrade planning because the impacted system handles sensitive clinical and practice data.

Executive priority

Treat as a near-term remediation item for any healthcare or practice-management environment using OpenEMR. The issue requires authentication, but the potential impact includes sensitive data compromise and operational disruption. Upgrade before 8.0.0 deployments remain broadly accessible.

Technical view

CVE-2026-25746 is CWE-89 SQL injection in OpenEMR prescription listing due to insufficient input validation. It affects OpenEMR versions prior to 8.0.0 and is fixed in 8.0.0. CVSS 3.1 is 8.8: network, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to OpenEMR deployments below 8.0.0 where an attacker can authenticate. Internet-accessible portals, shared clinical environments, and weak account controls raise practical risk. Unauthenticated exposure is not indicated by the provided sources.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not show active exploitation in the wild. A public GitHub repository is referenced for this CVE, so defenders should assume awareness may increase. Avoid relying on obscurity or authentication alone.

Researcher notes

Focus review on the prescription listing path and the input validation changes in the referenced fix commit. Do not assume all SQL injection surfaces are covered beyond the advisory scope. Evidence supports affected versions before 8.0.0 and fix availability in 8.0.0.

Mitigation direction

  • Upgrade OpenEMR to version 8.0.0 or later.
  • Review the OpenEMR GitHub advisory for vendor guidance.
  • Restrict OpenEMR access to trusted networks where possible.
  • Audit and reduce unnecessary authenticated user accounts.
  • Monitor database and application logs for unusual prescription listing activity.

Validation and detection

  • Inventory OpenEMR instances and confirm their running versions.
  • Flag any OpenEMR deployment older than 8.0.0.
  • Confirm whether prescription functionality is enabled and reachable.
  • Review user account exposure and authentication controls.
  • Verify the vendor fix commit or package update is applied.
Prepared
Confidence
high
Sources
5

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

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-25746 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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
8Source 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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-25746Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
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.