OpenEMR before 8.3.0 IDOR via Portal OnsiteDocument Pid_Equals Mass-Assignment
OpenEMR before 8.3.0 is affected only when the patient portal is enabled. The fix is in 8.3.0. No vendor rating is given, so the CVSS score of 7.1 (high) is the only severity shown.
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 master with the patient portal enabled (before 8.3.0) Attacker must have a valid portal-patient session
- 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 OnsiteDocumentController::Query() that allows authenticated portal patients to read other patients' documents by overriding Pid_Equals criteria. Attackers can supply Pid_Equals, Pid_GreaterThan, or Pid_In request parameters to the onsitedocuments API to retrieve signed consent forms, signatures, and PHI of any patient.
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 master with the patient portal enabled (before 8.3.0) Attacker must have a valid portal-patient sessionUpgrade 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-124455
Is CVE-2026-124455 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?
A logged-in patient on the portal can read signed consent and HIPAA documents and their signatures belonging to other patients, including all other patients. These documents contain protected health information (PHI).Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124455?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.3.0 with the patient portal enabled. Check your installed OpenEMR version and whether the patient portal is turned on in your configuration. Exposure also requires a valid portal-patient session.Source: github.com, vulncheck.com
How do I fix CVE-2026-124455?
Upgrade to OpenEMR 8.3.0 or later, which is the listed fixed version.Source: github.com, vulncheck.com