LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24890: OpenEMR Portal Users Can Forge Provider Signatures

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, an authorization bypass vulnerability in the patient portal signature endpoint allows authenticated portal users to upload and overwrite provider signatures by setting `type=admin-signature` and specifying any provider user ID. This could potentially lead to signature forgery on medical documents, legal compliance violations, and fraud. The issue occurs when portal users are allowed to modify provider signatures without proper authorization checks. Version 8.0.0 fixes the issue.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenEMR versions before 8.0.0 let an authenticated patient portal user overwrite provider signatures. In a healthcare setting, this creates risk of forged medical documents, compliance failures, and fraud. The issue is fixed in OpenEMR 8.0.0.

Executive priority

Treat as high priority for healthcare environments using OpenEMR. The main business risk is document integrity and regulatory trust, not system outage. Upgrade planning should be prompt.

Technical view

CVE-2026-24890 is an authorization bypass in OpenEMR’s patient portal signature functionality. A low-privileged authenticated portal user could modify provider signature data without proper authorization checks. CVSS is 8.1 High, with network access, low complexity, and high confidentiality and integrity impact.

Likely exposure

Organizations running OpenEMR before 8.0.0 are potentially exposed, especially if patient portal accounts are enabled. The vulnerability requires authenticated portal access, not anonymous access.

Exploitation context

The provided sources do not show active exploitation, KEV listing, or public exploit availability. Abuse would require a valid portal user account and could affect trust in provider-signed records.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, and fixing commit. The root issue is missing authorization enforcement for provider signature modification by portal users. Do not assume compromise without logs or supporting evidence.

Mitigation direction

  • Upgrade OpenEMR to version 8.0.0 or later.
  • Review the GitHub security advisory for vendor guidance.
  • Assess whether provider signatures were changed unexpectedly before upgrade.
  • Preserve relevant logs if suspicious signature activity is found.

Validation and detection

  • Inventory OpenEMR instances and confirm version numbers.
  • Identify any OpenEMR deployment below version 8.0.0.
  • Confirm whether patient portal accounts are enabled.
  • Review audit records for unexpected provider signature updates.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24890 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-24890Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
openemropenemr< 8.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-285 · source CWE mapping

Improper Authorization

Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.