OpenEMR before 8.5.0 Stored SQL Injection via History Layout Field Identifiers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| openemr | openemr | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.287% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OpenEMR before 8.5.0 Stored SQL Injection via History Layout Field Identifiers | |
| First Time appeared |
Open-emr
Open-emr openemr |
|
| Weaknesses | CWE-89 | |
| CPEs | cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Open-emr
Open-emr openemr |
|
| References |
| |
| Metrics |
cvssV3_1
|
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')