OpenEMR stored SQL injection in History layout fields
openemr
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| openemr openemr |
|
|
Original description
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.
From the CVE record · VulnCheck
References
- github.com/openemr/openemr/security/advisories/GHSA-fq58-jp5g-x44qVendor advisory
- vulncheck.com/advisories/openemr-before-8.5.0-stored-sql-injection-via-history-layout-field-identifiersAdvisory
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/126xxx/CVE-2026-126425.json
- nvd.nist.gov/vuln/detail/CVE-2026-126425