OPENEMR · CVE-2026-124473 · Runtime
NO FIX YET · SEE WHAT TO DO
OpenEMR before 8.3.0 does not check that a SOAP note belongs to the patient and encounter named in an update request. An authenticated user with note permission can overwrite another patient's clinical note and reassign it to a different patient.
first public Aug 18, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Clinics and hospitals running OpenEMR older than 8.3.0 where staff have the encounters/notes permission. The attacker must already be a logged-in user; patients and unauthenticated visitors are not in the path.
Not affected if no-encounter-notes-permission, openemr-8.3.0-or-later
Who cares healthcare, openemr, self-hosted
8.3.0encounters/notes permission8.3.0 or laterOpenEMR before 8.3.0 contains a broken object-level authorization vulnerability in the SOAP note update API, which does not verify that the supplied SOAP note ID (sid) belongs to the supplied patient and encounter. Authenticated users with encounters/notes permission can send PUT requests to /api/patient/:pid/encounter/:eid/soap_note/:sid with another patient's sid to overwrite that clinical note and reassign its pid.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/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.