Public vulnerability disclosure

CVE-2026-103021

OpenEMR: Username Enumeration via Pre-Authentication User Settings Loading

publishedCWE-200CWE-203CWE-208

OpenEMR is a free and open source electronic health records and medical practice management application. From 6.0.0 until 8.3.0, interface/globals.php uses the unauthenticated authUser login parameter to populate temp_authuserid and load that account's user_settings before authentication succeeds. Existing usernames can therefore cause an additional database query and may apply visible customized settings, while nonexistent usernames skip that behavior. A remote unauthenticated actor can use timing or page differences to enumerate valid accounts for later credential attacks. This issue is fixed in version 8.3.0.

Technical severity5.3 mediumCVSS 3.1 · CNA: GitHub_M
Published2026-11-05Source updated 2026-11-09
Collected2026-11-094 attributed sources

Fixes and workarounds

Fix

openemr/openemr (composer): GitHub reports patched versions 8.3.0. Check the advisory for the affected release branch.

Source: GitHub GHSA-rr38-hpxq-wwff

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
openemr
openemr
>= 6.0.0, < 8.3.0 (affected) CNA: GitHub_M
openemr/openemr

openemr/openemr
composer
>=6.0.0 <=8.3.0 (affected, GitHub advisory range) GitHub GHSA-rr38-hpxq-wwff

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.3
medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCNA: GitHub_M
3.1 / 5.3
medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NNVD: [email protected]

Exploit evidence

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide