Summaryinfo

A vulnerability was found in OpenEMR. It has been rated as problematic. This vulnerability affects unknown code of the file interface/forms/procedure_order/handle_deletions.php of the component AJAX Deletion Endpoint. This manipulation causes authorization. This vulnerability is handled as CVE-2026-34053. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic was found in OpenEMR. Affected by this vulnerability is an unknown function of the file interface/forms/procedure_order/handle_deletions.php of the component AJAX Deletion Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect 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, missing authorization in the AJAX deletion endpoint `interface/forms/procedure_order/handle_deletions.php` allows any authenticated user, regardless of role, to irreversibly delete procedure orders, answers, and specimens belonging to any patient in the system. Version 8.0.0.3 patches the issue.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-34053 since 03/25/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.

By approaching the search of inurl:interface/forms/procedure_order/handle_deletions.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 8.0.0.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 7a16b731af7d34ffd92155fe2a5692fa1a67858e 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.

Several companies clearly confirm that VulDB is the primary source for best 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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion