CVE-2013-10044: OpenEMR ≤ 4.1.1 SQL Injection Privilege Escalation and RCE
Noroxi assessment
Priority: Plan (action score 40/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Because a ready-made attack tool exists, priority is at least “Plan”.
- Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 83.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An authenticated SQL injection vulnerability exists in OpenEMR ≤ 4.1.1 Patch 14 that allows a low-privileged attacker to extract administrator credentials and subsequently escalate privileges. Once elevated, the attacker can exploit an unrestricted file upload flaw to achieve remote code execution, resulting in full compromise of the application and its host system.
- Published
- Aug 1, 2025
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 83th percentile
- CWE
- CWE-89
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
- Ready-made attack tool
- 5 / 40 · floor: at least 40
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 8.7
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| open-emr | openemr | cpe:2.3:a:open-emr:openemr |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
OpenEMR Foundation OpenEMR
- up to and including 4.1.1 Patch 14affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- open-emr openemrup to 4.1.1 inclusive
Same product
open-emr: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17179An issue was discovered in OpenEMR before 5.0.1 Patch 7.60This week
- CVE-2020-19364OpenEMR 5.0.1 allows an authenticated attacker to upload and execute malicious PHP scripts through /controller.php.56Plan
- CVE-2019-14530An issue was discovered in custom/ajax_download.php in OpenEMR before 5.0.2 via the fileName parameter.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-32967May 23, 2025 · OpenEMR doesn't log password administration properly21Monitor
- ← EarlierCVE-2025-43860May 23, 2025 · OpemEMR Vulnerable to Stored XSS Attack in the Additional Address Section of Patient Demographics35Monitor
- Later →CVE-2021-47817Jan 21, 2026 · OpenEMR 5.0.2.1 - Remote Code Execution19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | exploit/unix/webapp/openemr_sqli_privesc_uploadOpenEMR 4.1.1 Patch 14 SQLi Privilege Escalation Remote Code Executionexploit | 2013-09-16 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-4338 d
- Published
- TodayNov 16, 2026+472 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- xistencefinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-22611120 days apartOpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php, \controllers\C_Pharmacy.class.php and…41Plan
- CVE-2026-25746208 days apartOpenEMR has SQL Injection Vulnerability36Monitor
- CVE-2026-32127222 days apartSQL Injection Vulnerability in ajax graphs library (OpenEMR)35Monitor
- CVE-2026-29187236 days apartOpenEMR Vulnerable to Authenticated Blind Boolean-Based SQL Injection in new_search_popup.php35Monitor
- CVE-2026-33910236 days apartOpenEMR has a SQL Injection Vulnerability in patient selection35Monitor
- CVE-2026-33917236 days apartOpenEMR has SQL Injection in CAMOS Form35Monitor
Not on record for this CVE: patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS 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:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.