Security readout for executives and security teams
Plain-English summary
OpenEMR before 8.0.0 lets a logged-in user access or change DICOM viewer state for documents they should not control. The issue is an authorization gap around document IDs. For healthcare environments, this matters because imaging-related annotations or viewer settings may be exposed or altered across patient or encounter boundaries.
Executive priority
Prioritize remediation for clinical systems running affected OpenEMR versions, especially where multiple users access imaging workflows. The vulnerability can cross patient or encounter authorization boundaries, creating privacy and integrity risk, but available sources do not indicate public exploitation.
Technical view
CVE-2026-25927 is a CWE-639 authorization flaw in OpenEMR’s DICOM viewer state API. The API accepts a doc_id for upload or state save/load without confirming the document belongs to the user’s authorized patient or encounter. An authenticated attacker can enumerate document IDs to read or modify viewer state. Fixed in OpenEMR 8.0.0.
Likely exposure
Organizations running OpenEMR versions earlier than 8.0.0 and using DICOM viewer state functionality are potentially exposed. The attacker must already be authenticated, but no user interaction is required.
Exploitation context
The provided sources do not report active exploitation, and this CVE is not marked KEV. Exploitation requires valid OpenEMR credentials and relies on accessing unauthorized document IDs through the affected API behavior.
Researcher notes
This is an IDOR/BOLA-style object authorization issue mapped to CWE-639. Focus validation on whether doc_id access is scoped to the authenticated user’s permitted patient or encounter. Avoid assuming image file access; the sourced description specifically covers DICOM viewer state such as annotations and view settings.
Mitigation direction
- Upgrade OpenEMR to version 8.0.0 or later.
- Review the OpenEMR security advisory for vendor-specific guidance.
- Limit DICOM viewer access to necessary trusted users until upgraded.
- Monitor for unusual access to DICOM viewer state or document IDs.
Validation and detection
- Inventory OpenEMR deployments and identify versions earlier than 8.0.0.
- Confirm whether DICOM viewer state functionality is enabled or used.
- Verify OpenEMR has been upgraded to 8.0.0 or later.
- Review role assignments for users with DICOM viewer access.
- In a safe test environment, confirm users cannot access unauthorized document state.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2026-25927 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N2.84.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openemr/openemr/security/advisories/GHSA-qj9f-x7v2-hrr7CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.