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. |
| Impact | The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N) indicates network-accessible vulnerability with high attack complexity and high privilege requirements, which significantly constrains real-world exploitability despite the high confidentiality and integrity impacts. The requirement for high privilege (PR:H) suggests this is an insider threat or post-authentication exploitation scenario, substantially limiting the practical attack surface compared to unauthenticated vulnerabilities. The high complexity (AC:H) further reduces exploitation probability. However, the complete lack of availability impact (A:N) and the bounded scope suggest this is a targeted data exfiltration or tampering risk rather than a denial-of-service vector. For healthcare organizations, the high confidentiality and integrity impacts on protected health information (PHI) elevate the actual business risk above the numerical CVSS score. Without confirmed EPSS or KEV status data in the provided intelligence, organizations should assume standard exploitation difficulty but prioritize patching due to healthcare regulatory requirements (HIPAA, etc.) and the sensitivity of electronic health records. |
| Exploit ScenarioDerived | An authenticated OpenEMR administrator or privileged user with access to the MedEx recall/reminder configuration interface could inject malicious SQL code through input fields that process recall parameters. For example, a crafted recall date or patient criteria field could contain SQL commands that break out of the intended query context and extract sensitive patient data such as medication lists, diagnoses, or social security numbers from the healthcare database. Given the high complexity and privilege requirements, this attack is most likely to occur through a disgruntled insider or a compromised administrative account rather than an external attacker, but the damage to patient privacy and data integrity would be substantial. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
OpenEMR versions prior to 8.0.0.3 contain a SQL injection vulnerability in the MedEx recall/reminder processing code where user-controlled variables are concatenated directly into SQL queries without parameterization or type casting. An authenticated attacker with high privileges can exploit this to extract, modify, or delete sensitive healthcare data from the database. While the CVSS score of 5.9 is moderate, the attack requires high privilege level (PR:H) and high complexity (AC:H), but the confidentiality and integrity impacts are severe given the medical context.
RemediationAI
Immediately upgrade OpenEMR to version 8.0.0.3 or later, which contains the parameterized query fixes for the MedEx module (see https://github.com/openemr/openemr/security/advisories/GHSA-6vx2-w9hw-prqj). For organizations unable to patch immediately, implement strict database access controls limiting SQL query execution to least-privileged service accounts, enforce network segmentation to restrict access to OpenEMR database ports to trusted internal systems only, and enable comprehensive SQL query logging and monitoring to detect anomalous database activity. Additionally, restrict administrative access to the MedEx configuration and processing features to only essential personnel. While these mitigations reduce attack surface, they do not eliminate the vulnerability and should be considered temporary measures only.
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
The vulnerability is classified as CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) and stems from unsafe string concatenation in database query construction within OpenEMR's MedEx module, which handles patient recall and reminder communications. The affected product (cpe:2.3:a:openemr:openemr:*:*:*:*:*:*:*:*) indicates all versions of OpenEMR are potentially affected through version 8.0.0.2. The MedEx processing code fails to use parameterized queries or prepared statements, instead directly interpolating user-supplied input into SQL commands. This classic SQL injection pattern allows attackers to break out of intended query logic and execute arbitrary SQL operations against the underlying database.
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:H/PR:H/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, several variables in the MedEx recall/reminder processing code are concatenated directly into SQL queries without parameterization or type casting, enabling SQL injection. Version 8.0.0.3 contains a patch.
Executive ViewAI
Organizations using OpenEMR should be aware of moderate risk from CVE-2026-33909, a SQL injection vulnerability rated CVSS 5.9. Exploitation could allow attackers to execute code or inject malicious input. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: deploy WAF rules, restrict network access, enable logging.
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