CVE-2018-15150 json
SQL injection vulnerability in interface/de_identification_forms/de_identification_screen2.php in versions of OpenEMR before 5.0.1.4 allows…
published 8y ago modified 4mo ago also EUVD-2018-7030
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
SQL injection vulnerability in interface/de_identification_forms/de_identification_screen2.php in versions of OpenEMR before 5.0.1.4 allows a remote authenticated attacker to execute arbitrary SQL commands via the 'temporary_files_dir' variable in interface/super/edit_globals.php.
Patch / fix
- github.com/openemr/openemr#1757 pull request
- open-emr.org/wiki/index.php/OpenEMR_Patches advisory
Is CVE-2018-15150 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.38% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- insecurity.sh https://insecurity.sh/reports/openemr.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/openemr/openemr/pull/1757/files
third-party-advisory
-
open-emr.org
/wiki/index.php/OpenEMR_Patches
patch, vendor-advisory
-
insecurity.sh
/reports/openemr.pdf
exploit, third-party-advisory
-
databreaches.net
/openemr-patches-serious-vulnerabilities-uncovered-by-project-insecurity/
third-party-advisory
Sources
- CVE List CVE-2018-15150
- NVD CVE-2018-15150
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.