OpenEMR before 8.3.0 BOLA via portal_custom_report.php Exposes Patient Problem Lists
Affects OpenEMR versions before 8.3.0, where an authenticated portal patient can read other patients' problem list entries. 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 are affected. Deployments with IPPF configured also expose family-planning and contraceptive records.
- 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 a broken object level authorization vulnerability in portal/report/portal_custom_report.php that allows authenticated portal patients to read other patients' problem list entries. Attackers can enumerate sequential IDs in issue_ parameter names to retrieve other patients' problem titles, clinical notes, ICD diagnosis codes, and IPPF contraceptive 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
- 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 are affected. Deployments with IPPF configured also expose family-planning and contraceptive records.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-124470
Is CVE-2026-124470 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 flaw is a broken object-level authorization check in portal_custom_report.php. A logged-in portal patient can read problem list entries belonging to other patients, including problem type, title, clinical notes, and ICD diagnosis codes. In deployments with IPPF configured, family-planning and contraceptive records are also exposed.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124470?
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. The installed version can be checked in the OpenEMR software. Deployments with IPPF configured are also exposed to the family-planning and contraceptive record exposure.Source: github.com, vulncheck.com
How do I fix CVE-2026-124470?
Upgrade OpenEMR to 8.3.0, which contains the fix. The sources provided do not list a workaround.Source: github.com, vulncheck.com