Security readout for executives and security teams
Plain-English summary
OpenEMR before 8.0.0 lets any signed-in user view the full internal message list, not just administrators. In a healthcare system, those messages may contain sensitive operational or patient-related information. The issue is patched in OpenEMR 8.0.0.
Executive priority
Treat as a timely healthcare privacy issue, especially where many staff accounts exist. Prioritize upgrading affected OpenEMR systems, but this is not currently supported as an internet-scale unauthenticated attack.
Technical view
The Message Center accepted a “show all” request option and passed it to getPnotesByUser(), returning all users’ internal notes. The backend failed to enforce an administrator check before honoring that option. This is CWE-639, with CVSS 4.0 score 5.7.
Likely exposure
Organizations running OpenEMR versions earlier than 8.0.0 are potentially exposed if untrusted or lower-privileged authenticated users can access the Message Center.
Exploitation context
Exploitation requires a valid OpenEMR account. No active exploitation is indicated by KEV or the provided sources. Impact is confidentiality-focused: broad internal message disclosure without reported integrity or availability impact.
Researcher notes
Evidence points to broken authorization in the Message Center. The vendor advisory and commit identify the affected path and patch. Sources do not provide evidence of exploitation in the wild or additional affected products.
Mitigation direction
- Upgrade OpenEMR to version 8.0.0 or later.
- Review the OpenEMR security advisory for vendor guidance.
- Limit Message Center access to trusted users until patched.
- Review internal message content for sensitive data exposure risk.
Validation and detection
- Inventory OpenEMR instances and confirm versions.
- Verify vulnerable instances are upgraded to 8.0.0 or later.
- Confirm non-admin users cannot view all internal messages.
- Review application logs for unusual broad message access.
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-25220 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
- Medium
- CVSS
- 5.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.7MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openemr/openemr/security/advisories/GHSA-phcp-7qjx-83cmCVE reference · x_refsource_CONFIRM
- https://github.com/openemr/openemr/commit/9f2c44fc88fc051fcf0b6922c373977543e6b2afCVE reference · x_refsource_MISC
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.