Read the docs

Token replay and PIN brute force in OpenEMR one-time authentication

Priority HIGH 81CWE-307Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-307.

Summary

OpenEMR from 7.0.1 before 8.4.0 does not limit repeated authentication attempts in its one-time authentication code (CWE-307). The code ignores the single-use and access count settings, never revokes used tokens, and checks the login PIN without rate limiting or strict comparison. A remote attacker with no privileges who captures a token can replay it or guess the PIN without limit to open patient portal sessions that expose health data.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00351 29th percentileScored 2026-11-16
Fix Fixed openemr (openemr): 8.4.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
openemropenemr7.0.1 to before 8.4.08.4.0Patch availableCNA
  • openemr Vendoropenemr Affected 7.0.1 to before 8.4.0 Fixed in 8.4.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*——Open-Emr
  • cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* Versions — — ·Open-Emr

Remediation

Update OpenEMR to version 8.4.0, which is the fixed version.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA openemr (openemr) Fixed in 8.4.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    openemr 8.4.0

    15 records Highest priority Priority HIGH 6 HIGH, 5 MEDIUM, 4 LOW

    Other records, highest priority first

    • TI-2026-86844 Missing authorization in OpenEMR portal onsite-document APIsPriority HIGH 73
    • TI-2026-86843 Improper authorization in OpenEMR REST API lets staff forge prescriptionsPriority HIGH 73
    • TI-2026-86840 Authorization bypass in OpenEMR exposes FHIR questionnaire answersPriority HIGH 73

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-124445
  2. 2026-11-08 Alias added: GHSA-9cwc-jcxx-r43v
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-91365 OpenEMR OAuth scope flaw exposes FHIR Patient records to attackers CVSS 4.0CRITICAL 9.3
  • TI-2026-24664 SQL Injection Vulnerability in ajax graphs library (OpenEMR) CVSS 3.1HIGH 8.8
  • TI-2026-85645 Missing access checks in OpenEMR let users reassign documents CVSS 3.1CRITICAL 9.6
  • TI-2026-28796 OpenEMR 8.2.0 Remote Code Execution via CategoryTree eval() Injection CVSS 4.0CRITICAL 9.4
  • TI-2026-20308 OpenEMR's payments gateway_api_key secret rendered into client JS code CVSS 3.1CRITICAL 9.6
  • TI-2026-20093 OpenEMR has SQL Injection in Patient API Sort Parameter CVSS 3.1CRITICAL 10.0
See all 277 →

Sources