Skip to main content
CVE-2026-124451VulnerabilityPublished

OpenEMR before 8.4.0 contains an authorization bypass vulnerability in its SMART on FHIR implementation because

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-124451· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 8.4.0 when convenient.

Data as of 8 Nov 2026, 18:03 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.0
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 8.4.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 8 Nov 2026.

What to do

Upgrade openemr and openemr/openemr to 8.4.0.

Affected software

ProductAffectedFixed in
openemropenemrAffected
  • <8.4.0
Fixed in
  • 8.4.0
GitHubopenemr/openemrpkg:github/openemr/openemrOther threatsAffected
  • <8.4.0
Fixed in
  • 8.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in OpenEMR version 8.4.0 and later. Users should upgrade to version 8.4.0 or newer to remediate this authorization bypass vulnerability. No vendor advisory or patch links are provided, so confirm patch availability from official OpenEMR sources before upgrading.

Description

OpenEMR versions prior to 8.4.0 have an authorization bypass vulnerability in the SMART on FHIR implementation. The function checkUserHasAccessToPatient() in BearerTokenAuthorizationStrategy.php incorrectly always returns true, allowing authenticated users or malicious SMART apps to manipulate token launch context. This enables unauthorized read and write access to other patients' FHIR resources.

References

Community reviews

Loading reviews…