OpenEMR: Broken Access Control in controller.php Enables Insurance Routing Credential Hijack and PHI Enumeration
Affects OpenEMR versions before 8.3.0 when requests use the explicit controller.php dispatch route handled by Controller::dispatch(). CVSS rates it High (8.1); no vendor rating is given. Fixed in 8.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 8.3.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Request uses the explicit controller.php dispatch route (controller parameter) handled by Controller::dispatch(), rather than the nested practice_settings route.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
OpenEMR, a free electronic health records and medical practice management application, has a broken access control flaw in its controller.php dispatcher that lets a remote attacker with a low-privilege login change insurance-routing hosts and credentials or enumerate patient names, dates of birth, and identifiers. The flaw can be reached over the network with only a low-privilege account and no user interaction.
Read the original description
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, library/classes/Controller.class.php allows explicit controller.php dispatch to controllers missing from CONTROLLER_ACL_MAP, and checkControllerAcl() returns without enforcing any permission for those entries. A low-privilege authenticated user can invoke C_X12Partner::edit_action_process() to create or alter insurance-routing hosts and credentials, or invoke C_PatientFinder::find_action_process() to enumerate patient names, dates of birth, and identifiers. The shared fail-open dispatcher root cause also exposes other administrative controllers that were intended to be reached through ACL-gated Practice Settings routes. This issue is fixed in version 8.3.0.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Request uses the explicit controller.php dispatch route (controller parameter) handled by Controller::dispatch(), rather than the nested practice_settings route.Upgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- openemr openemr
fixed in 8.3.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115573
Is CVE-2026-115573 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A low-privilege logged-in user can send a request through the controller.php route that bypasses the access check meant to block them. This lets them change X12 claims-routing partner settings, including SFTP and API credentials and endpoints. It also lets them search and dump every patient's name, date of birth, and patient or public ID across the practice.Source: github.com
Which versions are affected by CVE-2026-115573?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.3.0 are affected when requests use the explicit controller.php dispatch route (the controller parameter) handled by Controller::dispatch(). The nested practice_settings route is not the path described here. To check your version, look at the OpenEMR version shown in the admin interface or the version file in the installation.Source: github.com
How do I fix CVE-2026-115573?
Upgrade OpenEMR to version 8.3.0 or later, which contains the fix. No workaround is listed in the facts provided.Source: github.com