OpenEMR before 8.4.0 FHIR Patient Compartment Bypass via Person Endpoint
Affects OpenEMR before 8.4.0 with the FHIR API enabled, where a patient-portal SMART token holding patient/Person.read scope can read staff demographics. Fixed in 8.4.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.4.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. FHIR API enabled on OpenEMR master (before 8.4.0) Attacker needs a valid patient-portal SMART access token Token must hold patient/Person.read scope, from a confidential patient-only SMART app
- 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.4.0 contains an authorization bypass vulnerability in the FHIR GET /fhir/Person/:uuid route that allows patient-portal users to read any staff member's demographics by bypassing compartment enforcement. Attackers holding a patient SMART token with patient/Person.read can harvest staff Person UUIDs from Appointment references to retrieve names, home addresses, phone numbers, and personal emails.
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.
FHIR API enabled on OpenEMR master (before 8.4.0) Attacker needs a valid patient-portal SMART access token Token must hold patient/Person.read scope, from a confidential patient-only SMART appUpgrade to a fixed version: 8.4.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.4.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-124458
Is CVE-2026-124458 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?
Patient-portal users can read the demographics of any staff member, including names, home addresses, phone numbers and personal emails, because the patient compartment check is bypassed.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124458?
openemr: before 8.4.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.4.0 with the FHIR API enabled are covered. The attack needs a valid patient-portal SMART access token with patient/Person.read scope, issued to a confidential patient-only SMART app. To check a setup, look at the OpenEMR version in the installation and whether the FHIR API is enabled in its settings.Source: github.com, vulncheck.com
How do I fix CVE-2026-124458?
Upgrade OpenEMR to version 8.4.0 or later, which contains the fix.Source: github.com, vulncheck.com