CVE-2026-124464 · Other
NO FIX YET · SEE WHAT TO DO
OpenEMR before 8.4.0 lets a patient-scoped SMART token read other patients' questionnaire responses, because the FHIR QuestionnaireResponse service skips the patient filter. An attacker holding such a token can fetch a response by UUID or list the unfiltered bundle to obtain other patients' clinical assessment answers.
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 health organizations running OpenEMR 8.3 or earlier with the FHIR API and SMART patient tokens in use. A patient-scoped token holder can see other patients' questionnaire answers, so systems that do not issue patient SMART tokens are less exposed. The sources do not say whether default configurations enable this scope.
Not affected if no-patient-smart-tokens, openemr-8.4.0-or-later
Who cares fhir, healthcare, openemr, self-hosted, smart-on-fhir
8.4.0 are affected.patient/QuestionnaireResponse.rs scope.8.4.0 or later.OpenEMR before 8.4.0 contains an authorization bypass vulnerability that allows patient-scoped SMART tokens to read other patients' questionnaire responses because FhirQuestionnaireResponseService does not implement IPatientCompartmentResourceService. Attackers holding a patient/QuestionnaireResponse.rs token can request responses by uuid or list the unfiltered bundle to obtain cross-patient clinical assessment answers.
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.