Quick answers
- Is CVE-2026-103021 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103021 being exploited in the wild.
- How severe is CVE-2026-103021?
- Medium severity, with a CVSS score of 5.3, published 5 November 2026.
- Which products and versions are affected?
- OpenEMR Project OpenEMR 6.0.0 to 8.3.0.
- Is there a fix for CVE-2026-103021?
- Yes: fixed in 8.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103021 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-103021?
- Check whether you run OpenEMR Project OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 8.3.0
Technical details
The interface/globals.php file processes the authUser login parameter before authentication completes, causing the application to load user_settings and trigger database queries for valid usernames but not for invalid ones. This timing or behavioral difference allows account enumeration via unauthenticated network requests. The vulnerability stems from pre-authentication processing of user input that should only occur after successful login.
Affected products
- OpenEMR Project OpenEMR 6.0.0 to 8.3.0
Timeline
- 2026-11-05: disclosed