Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to OpenEMR instance
-
DeliverySubmit crafted SQL payload via ajax_save CAMOS form
-
ExploitBypass input validation in form processor
-
ExecutionExecute arbitrary SQL queries
-
ImpactExtract or modify sensitive health records
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 must have login credentials to access the CAMOS form ajax_save endpoint. Remote exploitation via HTTP; no victim interaction needed beyond attacker possessing valid authentication. |
| Impact | The CVSS v3.1 score of 8.8 (High) reflects significant technical impact with network attack vector (AV:N), low complexity (AC:L), and high impact to confidentiality, integrity, and availability (C:H/I:H/A:H). However, the requirement for low-privilege authentication (PR:L) provides partial mitigation as the attacker must first obtain valid credentials. Real-world risk signals are mixed: EPSS probability of 0.03% (8th percentile) indicates very low observed exploitation likelihood in the wild, and no public exploit identified at time of analysis. The vulnerability is not listed in CISA KEV, confirming no known active exploitation campaigns. Despite the high CVSS score, the combination of authentication requirements, low EPSS probability, patch availability, and absence of public exploits suggests this is a moderate priority rather than emergency-critical. Organizations using OpenEMR should prioritize patching within standard maintenance windows, with accelerated timelines for internet-facing instances or environments with weak credential controls where the PR:L barrier is more easily overcome. |
| Exploit ScenarioDerived | An authenticated attacker with low-privilege credentials (such as a standard clinical user account) accesses the OpenEMR CAMOS form interface and intercepts the ajax_save request. By injecting malicious SQL syntax into vulnerable form parameters, the attacker executes arbitrary database queries to extract the entire patient database containing protected health information (PHI), modify medical records to alter treatment documentation, or delete critical data causing service disruption. The attack requires no user interaction and can be automated once valid credentials are obtained through phishing, credential stuffing, or insider access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
SQL injection in OpenEMR versions prior to 8.0.0.3 enables authenticated attackers to execute arbitrary SQL commands through the CAMOS form's ajax_save functionality, potentially leading to complete database compromise including extraction of sensitive health records, data modification, and service disruption. The vulnerability requires low-privilege authentication (PR:L) with no user interaction (UI:N) and is network-exploitable (AV:N), though EPSS assigns only 0.03% (8th percentile) exploitation probability and no public exploit identified at time of analysis. Vendor-released patch available in version 8.0.0.3.
RemediationAI
Upgrade OpenEMR to version 8.0.0.3 or later, which contains the fix for this SQL injection vulnerability as documented in the release notes at https://github.com/openemr/openemr/releases/tag/v8_0_0_3. The specific remediation code is available in commit 4d48821d18e4125508d8217c43b09233c7f7e17f at https://github.com/openemr/openemr/commit/4d48821d18e4125508d8217c43b09233c7f7e17f for administrators who need to verify the patch or apply it manually. Until patching is completed, implement defense-in-depth measures including restricting access to the CAMOS form module to only essential personnel, enforcing strong authentication policies, monitoring database query logs for SQL injection patterns, and deploying web application firewall rules to detect and block SQL injection attempts targeting the ajax_save endpoint. Review and rotate database credentials as a precautionary measure if exploitation is suspected.
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
OpenEMR is an open-source electronic health records (EHR) and medical practice management system widely deployed in healthcare settings. The vulnerability affects cpe:2.3:a:openemr:openemr:*:*:*:*:*:*:*:* (versions prior to 8.0.0.3) and is classified as CWE-89 (SQL Injection), indicating insufficient input validation and sanitization in the ajax_save endpoint of the CAMOS (Computer Aided Medical Ordering System) form module. Attackers can inject malicious SQL commands through form parameters that are improperly handled during database queries, allowing direct interaction with the underlying database layer. The CAMOS module is used for clinical documentation and order entry, making it a critical component that handles sensitive patient health information subject to HIPAA and similar regulations.
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:H
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. Versions prior to 8.0.0.3 contais a SQL injection vulnerability in the ajax_save CAMOS form that can be exploited by authenticated attackers. The vulnerability exists due to insufficient input validation in the ajax_save page in the CAMOS form. Version 8.0.0.3 patches the issue.
Executive ViewAI
OpenEMR deployments running versions prior to 8.0.0.3 contain a SQL injection vulnerability in the CAMOS form module that allows low-privilege authenticated users to execute arbitrary database commands without user interaction. This directly threatens the confidentiality, integrity, and availability of protected health information (PHI) stored in OpenEMR databases, creating potential HIPAA compliance violations and operational disruption across affected healthcare organizations.
Apply vendor patch to version 8.0.0.3 or later. If immediate patching is not feasible: disable or restrict network access to the CAMOS form ajax_save endpoint via WAF rules or network segmentation; enforce principle of least privilege by removing non-essential database user permissions; implement database activity monitoring (DAM) on healthcare-sensitive tables to detect anomalous SQL queries; audit and revoke unnecessary low-privilege user accounts with OpenEMR access.
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
VulDB
Exploit-DB