OpenEMR before 5.0.2 allows SQL Injection in interface/forms/eye_mag/save.php.

published 2019-08-02 7y ago modified 2026-06-17 4mo ago also EUVD-2019-5699

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 28.1%; EPSS 28.1% chance of exploitation in 30 days, percentile 98%
public exploits: 0; none known

Patch / fix

fixed in 1 links 1

open-emr openemr 5.0.2

github.com/openemr/openemr#2592 pull request

Is CVE-2019-14529 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 Fencer

Exploit prediction

28.09% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/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/2592
product
github.com /Wezery/CVE-2019-14529
third-party-advisory

Sources

CVE List CVE-2019-14529
NVD CVE-2019-14529

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.