OpenEMR up to 8.0.0.2 get_claim_file.php authorization

Summaryinfo

A vulnerability marked as critical has been reported in OpenEMR. The impacted element is an unknown function of the file interface/billing/get_claim_file.php. The manipulation leads to authorization. This vulnerability is referenced as CVE-2026-33918. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in OpenEMR and classified as critical. This issue affects an unknown code of the file interface/billing/get_claim_file.php. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is 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, the billing file-download endpoint `interface/billing/get_claim_file.php` only verifies that the caller has a valid session and CSRF token, but does not check any ACL permissions. This allows any authenticated OpenEMR user — regardless of whether they have billing privileges — to download and permanently delete electronic claim batch files containing protected health information (PHI). Version 8.0.0.3 patches the issue.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-33918 since 03/24/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

By approaching the search of inurl:interface/billing/get_claim_file.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 f6d98d0102df0a8f131be560d9208fb65fba6188 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.

The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202603-5527). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion