CVE-2026-33917 OpenEMR has SQL Injection in CAMOS Form
Authenticated attackers can exploit SQL injection in the CAMOS form to read or modify database records in OpenEMR.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-33917?
CVE-2026-33917 is a high-severity SQL injection vulnerability in Open-Emr Openemr, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
OpenEMR is a free and open source electronic health records and medical practice management application. Versions prior to 8.0.0.3 contais a SQL injection vulnerability in the ajax_save CAMOS form that can be exploited by authenticated attackers. The vulnerability exists due to insufficient input validation in the ajax_save page in the CAMOS form. Version 8.0.0.3 patches the issue.
Weakness: CWE-89
Which versions are affected by CVE-2026-33917?
It affects 1 product.
Products include Open-Emr Openemr.
How do I fix CVE-2026-33917?
No fix has been published for CVE-2026-33917 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-33917 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33917 exists.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Open-Emr Openemr
- CVE-2026-24898 OpenEMR has an Unauthenticated MedEx Token Disclosure
- CVE-2026-24849 OpenEMR Arbitrary File Read Vulnerability
- CVE-2026-24908 OpenEMR has SQL Injection in Patient API Sort Parameter
- CVE-2022-2734 Improper Restriction of Rendered UI Layers or Frames in openemr/openemr
- CVE-2024-22611 SQL injection in n/a
Sources
Also known as GHSA-r6xq-mfwf-wgq8.