CVE-2024-22611
CVE-2024-22611 is a critical-severity vulnerability in Open-emr Openemr with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- EPSS exploit prediction: 6% (94th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2024-20145
- Weakness: CWE-89
- Affected product: Open-emr Openemr
- Published:
- Last modified:
Description
OpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php, \controllers\C_Pharmacy.class.php and \openemr\controller.php.
Frequently asked questions
- What is CVE-2024-22611?
- OpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php, \controllers\C_Pharmacy.class.php and \openemr\controller.php.
- How severe is CVE-2024-22611?
- CVE-2024-22611 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2024-22611 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2024-22611?
- CVE-2024-22611 affects Open-emr Openemr. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2024-22611?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- Does CVE-2024-22611 have an EU (EUVD) identifier?
- Yes. CVE-2024-22611 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-20145.
- When was CVE-2024-22611 published?
- CVE-2024-22611 was published on 2025-04-03 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:open-emr:openemr:7.0.2:*:*:*:*:*:*:*
More vulnerabilities in Open-emr Openemr
- CVE-2026-24898 — Critical (CVSS 10.0): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
- CVE-2026-124469 — Critical (CVSS 9.9): OpenEMR before 8.3.0 contains an SQL injection vulnerability in the Fee Sheet drug-inventory lookup…
- CVE-2026-24848 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. In 7.0.4 and…
- CVE-2026-24908 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
- CVE-2026-24849 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
- CVE-2024-37734 — Critical (CVSS 9.8): An issue in OpenEMR 7.0.2 allows a remote attacker to escalate privileges viaa crafted POST request using the noteid…
All CVEs affecting Open-emr Openemr →
Other CWE-89 (SQL Injection) vulnerabilities
- CVE-2026-124815 — Critical (CVSS 10.0): The Clockinator Lite WordPress plugin before 1.1.0 does not restrict access to several of its record deletion actions,…
- CVE-2026-105781 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL…
- CVE-2026-79849 — Critical (CVSS 10.0): Vulnerabilities in the affected interface of AOS-8 could allow an unauthenticated remote attacker to conduct SQL…
- CVE-2026-79848 — Critical (CVSS 10.0): Vulnerabilities in the affected interface of AOS-8 could allow an unauthenticated remote attacker to conduct SQL…
- CVE-2026-55572 — Critical (CVSS 10.0): e107 is a content management system (CMS). Prior to 2.3.7, the bundled alt_auth plugin's otherdb and e107db…
- CVE-2026-12260 — Critical (CVSS 10.0): SQL injection in the NetBoard CRM demo platform; specifically, the vulnerable component is the ‘user-name’ POST…