OpenEMR before 8.3.0 Cross-Patient IDOR via Encounter Form Viewers and Save Handlers
Affects OpenEMR versions before 8.3.0, where encounter form viewers and save handlers lack patient and encounter ownership checks. Fixed in 8.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.3.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OpenEMR versions before 8.3.0 (affected range per VulnCheck; GitHub lists master at commit 1d39d67). Attacker must be an authenticated user with an active encounter (a normal clinical role, not admin). The affected form view and save endpoints lack patient/encounter ownership checks.
- 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? →
- 17/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
Summary
OpenEMR before 8.3.0 contains an insecure direct object reference vulnerability in many encounter-form view and save endpoints that lack patient/encounter ownership checks. Authenticated clinical users can enumerate sequential form id values in requests such as soap/view.php and save.php to read and overwrite other patients' clinical records.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- 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 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OpenEMR versions before 8.3.0 (affected range per VulnCheck; GitHub lists master at commit 1d39d67). Attacker must be an authenticated user with an active encounter (a normal clinical role, not admin). The affected form view and save endpoints lack patient/encounter ownership checks.Upgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.3.0
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124459
Is CVE-2026-124459 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Authenticated clinical users can read and overwrite other patients' clinical records by enumerating sequential form IDs. The encounter form view and save endpoints do not check that the form belongs to the patient and encounter being accessed.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124459?
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, per VulnCheck's range; GitHub lists master at commit 1d39d67 as affected too. The exposure requires an active encounter and a normal clinical role, not admin, so compare the installed OpenEMR version number against 8.3.0.Source: vulncheck.com, github.com
How do I fix CVE-2026-124459?
Upgrade to OpenEMR 8.3.0 or later, which is the listed fixed version. No workaround is listed in the facts.Source: vulncheck.com, github.com