LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25930: OpenEMR's Printable LBF Endpoint Leaks Arbitrary Patient Forms

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, the Layout-Based Form (LBF) printable view accepts `formid` and `visitid` (or `patientid`) from the request and does not verify that the form belongs to the current user’s authorized patient/encounter. An authenticated user with LBF access can enumerate form IDs and view or print any patient’s encounter forms. Version 8.0.0 fixes the issue.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OpenEMR versions before 8.0.0 can let a logged-in user with Layout-Based Form access view or print encounter forms for patients they are not authorized to access. The main business risk is unauthorized disclosure of sensitive patient information. The vendor advisory states version 8.0.0 fixes the issue.

Executive priority

Treat as a timely healthcare privacy remediation item. It is not described as actively exploited, but it can expose patient encounter forms to authenticated users beyond their authorization. Prioritize upgrade planning for OpenEMR environments handling regulated patient data.

Technical view

The LBF printable view accepts request-supplied formid and visitid, or patientid, without verifying the form belongs to an authorized patient or encounter. This is CWE-639 authorization bypass through user-controlled keys. CVSS is 6.5: network-accessible, low complexity, low privileges, no user interaction, high confidentiality impact.

Likely exposure

Organizations running OpenEMR before 8.0.0 and using Layout-Based Forms are potentially exposed. Abuse requires an authenticated account with LBF access. Exposure is primarily internal or account-compromise driven, not unauthenticated internet-wide access based on the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation. The vulnerability is practical for a low-privileged authenticated user because it involves enumerating identifiers and missing ownership checks. The impact is data confidentiality, not system takeover.

Researcher notes

Validation should focus on authorization boundaries in the LBF printable view and whether form, visit, and patient identifiers are checked against the current user’s permitted patient or encounter. Avoid broad identifier testing in production unless explicitly authorized. The referenced commit is the best source for patch-diff review.

Mitigation direction

  • Upgrade OpenEMR to version 8.0.0 or later.
  • Review the GitHub security advisory for vendor-specific guidance.
  • Restrict LBF access to users with a current business need.
  • Review patient data access controls and role assignments.
  • Monitor for unusual printable-form access patterns.

Validation and detection

  • Inventory OpenEMR deployments and confirm installed versions.
  • Identify systems running OpenEMR earlier than 8.0.0.
  • Confirm whether Layout-Based Forms are enabled and used.
  • Review which roles or users have LBF access.
  • Check audit logs for unusual form printing or cross-patient access.
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-639: 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
cve · low confidence lookup

CVE-2026-25930 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-25930Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.