Database read and write via MedEx SQL injection
Published Mar 25, 2026 · Updated Mar 25, 2026
SQL injection in OpenEMR before 8.0.0.3 allows remote authenticated users to read or modify patient records through MedEx processing. The MedEx generate() method places stored facility IDs and fields from MedEx API responses into IN, INTERVAL, and LIMIT clauses without consistent validation or parameterization. MedEx must be enabled; exploitation requires administrator control of its preferences or a compromised MedEx account or API connection.
Summary
What happened
SQL injection in OpenEMR before 8.0.0.3 allows remote authenticated users to read or modify patient records through MedEx processing. The MedEx generate() method places stored facility IDs and fields from MedEx API responses into IN, INTERVAL, and LIMIT clauses without consistent validation or parameterization. MedEx must be enabled; exploitation requires administrator control of its preferences or a compromised MedEx account or API connection.
The record
- CVE
- CVE-2026-33909
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.0.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo