LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27943: OpenEMR's Eye Exam View Trusts form_id Without Verifying Patient/Encounter Ownership

OpenEMR is a free and open source electronic health records and medical practice management application. In versions up to and including 8.0.0, the eye exam (eye_mag) view loads data by `form_id` (or equivalent) without verifying that the form belongs to the current user’s patient/encounter context. An authenticated user can access or edit any patient’s eye exam by supplying another form ID; in some flows the session’s active patient may also be switched. A fix is available on the `main` branch of the OpenEMR GitHub repository.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OpenEMR versions through 8.0.0 may let a logged-in user view another patient’s eye exam record by referencing its form ID. This is a patient privacy issue in an electronic health records system. Public sources say a fix exists on OpenEMR’s main GitHub branch, but do not state active exploitation.

Executive priority

Prioritize for healthcare environments because it can expose patient clinical data to authenticated but unauthorized users. Treat as a medium-severity privacy and compliance risk, especially where many staff accounts exist or role boundaries are broad.

Technical view

The eye exam eye_mag view trusts a supplied form_id or equivalent without confirming it belongs to the current patient and encounter context. This is CWE-639, an authorization bypass through user-controlled key. CVSS 3.1 is 6.5: network, low complexity, low privileges, no user interaction, high confidentiality impact.

Likely exposure

Organizations running OpenEMR version 8.0.0 or earlier with authenticated users able to access the eye exam module should treat this as relevant. Exposure depends on role permissions and whether eye_mag functionality is enabled or used.

Exploitation context

An attacker needs valid OpenEMR credentials. The issue is not listed in CISA KEV, and the provided sources do not report active exploitation. The main concern is unauthorized access to patient eye exam data, with possible workflow side effects described by the advisory.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, and referenced commit. Sources indicate the fix is on the main branch, but do not confirm a packaged release. Avoid assuming unauthenticated access or public exploitation. Validate authorization checks around patient, encounter, and form ownership.

Mitigation direction

  • Review the OpenEMR advisory and commit for the official fix status.
  • Upgrade or apply the vendor-provided fix when available for your deployment path.
  • Limit eye exam module access to users with a business need.
  • Review role permissions for low-privileged authenticated users.
  • Monitor OpenEMR and GitHub advisories for a tagged release or backport.

Validation and detection

  • Identify all OpenEMR instances and confirm their versions.
  • Check whether any instance runs version 8.0.0 or earlier.
  • Confirm whether the eye_mag eye exam functionality is enabled.
  • Review access roles allowed to view or edit eye exams.
  • Audit recent eye exam access for unexpected patient-context changes or mismatches.
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-27943 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-27943Attack 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.