CVE-2026-104134 · Runtime
NO FIX YET · SEE WHAT TO DO
OpenEMR, an electronic health records application, has an endpoint that searches the person and patient tables without checking the user's permissions. A logged-in low-privilege user can enumerate names and receive patients' names, dates of birth, gender, phone numbers and email addresses.
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 deployment before 8.3.0 where users have accounts, since the flaw requires a low-privilege authenticated user. Clinics or hospitals that self-host OpenEMR are the main exposure; the risk is patient data exposure through the person search endpoint.
Not affected if no-user-accounts, version-8.3.0-or-later
Who cares healthcare, openemr, php, self-hosted
8.3.0 are affected.library/ajax/person_search_ajax.php in the installed application and confirm whether it performs an AclMain authorization check.8.3.0 or later.OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, the search_persons action in library/ajax/person_search_ajax.php validates CSRF but does not perform an AclMain authorization check before searching the person and patient_data tables. A low-privilege authenticated user can iterate name prefixes and receive patient first and last names, dates of birth, gender, phone numbers, and email addresses in JSON responses. This issue is fixed in version 8.3.0.
This page as .md ·
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.