Security readout for executives and security teams
Plain-English summary
OpenEMR versions before 8.0.0 let a logged-in patient portal user influence which patient record the payment page uses. This can expose another patient’s demographics, invoices, and payment history. The issue affects confidentiality most and has limited integrity impact. A fix is available in OpenEMR 8.0.0.
Executive priority
Prioritize remediation for healthcare environments using OpenEMR patient portal payments. The issue can expose protected patient and billing information to other authenticated portal users. Because a vendor fix exists, upgrade planning should be treated as a near-term privacy and compliance risk reduction task.
Technical view
In portal/portal_payment.php, OpenEMR overwrites the authenticated session patient ID with request-controlled pid or hidden_patient_code values. Because the page then uses that value without proper authorization, an authenticated portal user can perform horizontal privilege escalation/IDOR. CVSS is 7.1 high: network-accessible, low complexity, low privileges, no user interaction, high confidentiality impact.
Likely exposure
Organizations running OpenEMR before 8.0.0 with the patient portal and portal payment functionality exposed are likely affected. Exploitation requires a valid portal account, so exposure is primarily authenticated patient users rather than unauthenticated internet traffic.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. Abuse would require portal authentication and relies on improper trust of patient identifiers supplied in requests. The practical business concern is unauthorized access to patient billing and demographic information.
Researcher notes
This is CWE-639 authorization bypass through user-controlled key. The vulnerable behavior is specifically documented as request parameters replacing the session patient ID in portal/portal_payment.php. Avoid assuming broader OpenEMR modules are affected unless separately verified from vendor sources.
Mitigation direction
- Upgrade OpenEMR to version 8.0.0 or later.
- Review the GitHub advisory and vendor guidance for deployment-specific instructions.
- Restrict portal access where possible until upgraded.
- Review patient portal payment logs for unusual cross-patient access patterns.
Validation and detection
- Inventory OpenEMR instances and confirm versions are below or at 8.0.0.
- Confirm whether the patient portal and payment page are enabled.
- Verify the installed code includes the vendor fix commit or release 8.0.0.
- Check logs for unexpected portal payment access involving multiple patient identifiers.
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 lookupPrivilege 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 lookupCVE-2026-25147 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-mwmw-qxv3-8whhCVE reference · x_refsource_CONFIRM
- https://github.com/openemr/openemr/commit/d6ab3cd0b621b19b942cf49d2db2026e288aa214CVE 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.