CVE-2026-124458 · Runtime
NO FIX YET · SEE WHAT TO DO
OpenEMR before 8.4.0 fails to enforce the patient compartment on the FHIR GET /fhir/Person/:uuid route. A patient-portal user with a SMART token holding patient/Person.read can read any staff member's name, home address, phone number and personal email.
first public Sep 13, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Clinics and hospitals that run OpenEMR with the FHIR API and the patient portal enabled are exposed, since the flaw needs a patient-portal account with a SMART token that has patient/Person.read. Deployments without the FHIR API or patient portal, or with the portal disabled, are not described as affected by the sources.
Not affected if fhir-api-disabled, patient-portal-disabled
Who cares fhir, healthcare, openemr, self-hosted
8.4.0 or later.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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.