CVE-2026-104134: openemr · Missing Authorization
Affects openemrSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.3.0 when convenient.
Data as of 5 Nov 2026, 20:19 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 8.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade openemr to 8.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| openemropenemr | Affected
| Fixed in
|
Description
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.
References
- github.com/openemr/openemr/security/advisories/GHSA-xhfm-5pwg-3cxv (opens in a new tab)
- github.com/openemr/openemr/pull/13200 (opens in a new tab)
- github.com/openemr/openemr/commit/7973cab3fe3f2fd2374ed71c02605e3c93491c36 (opens in a new tab)
- github.com/openemr/openemr/releases/tag/v8_3_0 (opens in a new tab)