OpenEMR before 8.3.0 IDOR in Patient Portal PortalPatientController
Affects OpenEMR before 8.3.0, where an authenticated patient can read other patients' pending demographic change requests. CVSS rates it high. 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 (all versions from v5.0.1 through current are affected in the GitHub advisory)
- 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? →
- 15/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 PortalPatientController::Read() that allows authenticated patients to read other patients' pending demographic change requests. Attackers can supply another patient's ID in the patientId query string parameter to retrieve PHI including names, addresses, SSNs, and insurance information.
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
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 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 (all versions from v5.0.1 through current are affected in the GitHub advisory)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-124460
Is CVE-2026-124460 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?
The Patient Portal controller does not check that a logged-in patient is requesting their own records, so an authenticated patient can read other patients' pending demographic change requests. These can expose PHI such as names, addresses, SSNs and insurance information.Source: vulncheck.com
Which versions are affected by CVE-2026-124460?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
All OpenEMR versions before 8.3.0 are in the affected range, and the GitHub advisory lists every version from v5.0.1 onward. Compare your installed OpenEMR version number with 8.3.0 to see whether it falls in that range, and note that the bug is in the Patient Portal feature.Source: vulncheck.com
How do I fix CVE-2026-124460?
Upgrade to OpenEMR 8.3.0 or later, which contains the fix. No workaround is listed in the sources.Source: vulncheck.com