OpenEMR 7.0.1 before 8.4.0 OneTimeAuth Token Replay and PIN Brute Force
Affects OpenEMR 7.0.1 up to but not including 8.4.0 where the patient-portal OneTimeAuth login is in use. Fixed in 8.4.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.4.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenEMR, the electronic health records software, is affected in this range of releases, and an attacker can reach the flaw remotely without logging in or any user action. Using a captured one-time token or guessing the login PIN, an attacker can open patient-portal sessions that expose protected health information.
Read the original description
OpenEMR from 7.0.1 before 8.4.0 contains a flaw in src/Common/Auth/OneTimeAuth.php that ignores the enforce_onetime_use and max_access_count flags, never revokes consumed service_auth tokens, and checks login_pin without rate limiting or strict comparison. Attackers holding a captured token can replay it or brute-force the PIN to open patient-portal sessions exposing PHI.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.4.0.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- openemr openemr
From 7.0.1 · fixed in 8.4.0
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124445
Is CVE-2026-124445 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The OneTimeAuth patient-portal login stores two security policy flags that allow a captured valid service_auth token to be replayed, and the optional 6-digit PIN can be brute-forced. Each successful replay or PIN guess establishes a full patient-portal session and exposes that patient's PHI, such as name, DOB, SSN, medications and lab results.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124445?
openemr: from 7.0.1 before 8.4.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions 7.0.1 up to but not including 8.4.0 are in the affected range. The PIN brute-force variant applies only where a PIN is enforced in the FaxSMS invoice-payment flow, and the token replay variant involves the OneTimeAuth patient-portal login component. Compare your installed OpenEMR version with this range and check whether that login component is in use.Source: vulncheck.com, github.com
How do I fix CVE-2026-124445?
Upgrade to OpenEMR 8.4.0 or later, which is the fixed version listed in the advisory. The facts provided do not list a workaround.Source: vulncheck.com, github.com