CVE-2026-104139 · Runtime
NO FIX YET · SEE WHAT TO DO
OpenEMR, an electronic health records application, lets any logged-in user switch the active patient in their session without an access check. A low-privilege user can then download a rendered template containing another patient's demographics, allergies, medications and problem list.
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.
Any OpenEMR installation before 8.3.0 with user accounts that lack patient document access is exposed, since any authenticated user can reach the flawed endpoints. Installations where only fully trusted staff have logins carry less practical risk, but the flaw still crosses patient-access boundaries. Systems that do not run OpenEMR can skip it.
Not affected if no-untrusted-logins, openemr-8.3.0-or-later
Who cares healthcare, openemr, php, self-hosted
8.3.0 are listed as affected8.3.0OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, library/ajax/set_pt.php allows any authenticated user to set an arbitrary patient identifier in the active session without an ACL check, and interface/patient_file/download_template.php trusts that session value while enforcing only CSRF validation. A low-privilege user can select another patient and download a rendered document template containing the patient's demographics, encounter information, allergies, medications, and problem list despite lacking patients/docs access. This issue is fixed in version 8.3.0.
This page as ·
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.