OpenEMR up to 8.0.0.2 MedEx Recall sql injection

Summaryinfo

A vulnerability marked as critical has been reported in OpenEMR. Affected is an unknown function of the component MedEx Recall. This manipulation causes sql injection. The identification of this vulnerability is CVE-2026-33909. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in OpenEMR. Affected by this vulnerability is an unknown code of the component MedEx Recall. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, several variables in the MedEx recall/reminder processing code are concatenated directly into SQL queries without parameterization or type casting, enabling SQL injection. Version 8.0.0.3 contains a patch.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-33909 since 03/24/2026. The exploitation appears to be difficult. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

Upgrading to version 8.0.0.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 3d11d2fc1622147d4aa6fbca31a471e7402ffc65 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Business Process Management Software

Name

• OpenEMR

Version

• 2.8.1
• 2.8.2
• 3.1.0
• 3.2
• 3.2.0
• 4.0.0
• 4.1.0
• 4.1.1
• 5.0.0
• 5.0.0 Patch 1
• 5.0.1
• 5.0.1-6
• 5.0.1-dev
• 5.0.1.1
• 5.0.1.3
• 5.0.1.4
• 5.0.2
• 5.0.2.1
• 5.0.2.4
• 5.0.2.5
• 6.0.0
• 6.0.0-dev
• 6.0.0.0
• 6.0.0.2
• 6.0.0.4
• 6.1.0
• 6.1.0.1
• 7.0.0
• 7.0.0.1
• 7.0.0.2
• 7.0.1
• 7.0.2
• 7.0.2.1
• 7.0.3
• 7.0.3.1
• 7.0.3.4
• 7.0.4
• 7.3.0
• 8.0.0
• 8.0.0.1
• 8.0.0.2

License

• open-source

Website

• Product: https://github.com/openemr/openemr/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion