OpenEMR
OpenEMR before 8.5.0 Stored SQL Injection via History Layout Field Identifiers
OpenEMR before 8.5.0 contains a stored SQL injection vulnerability in which History layout field identifiers saved through edit_layout.php, including HIS fields and LBF source-H fields, are placed unvalidated into an INSERT statement for patients without a history_data row. Users with admin/super and patients/med write access can trigger history_save.php or LBF saves to execute SQL functions like SLEEP, tying up database workers or accessing data beyond their privileges.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.2high · scored by CNA · CWE-89
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
openemr openemr
- < 8.5.0
Fixed in 8.5.0
Mitigation
Upgrade openemr to 8.5.0 or later.
References
- Vendor advisory github.com/openemr/openemr/security/advisories…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.