Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25146 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Open-Emr Openemr. Its CVSS base score is 9.6 (Critical).
Operationally, ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25146 is a high-severity vulnerability in OpenEMR, a free and open source electronic health records and medical practice management application. Affecting versions from 5.0.2 up to but not including 8.0.0, the issue involves at least two code paths that render the gateway_api_key secret value in plaintext to the client. Classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), it carries a CVSS v3.1 base score of 9.6 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N), highlighting its critical potential impact.
A low-privileged remote attacker (PR:L) can exploit this vulnerability over the network with low complexity and no user interaction required. Successful exploitation leaks the gateway_api_key, enabling arbitrary money movement or broad account takeover of connected payment gateway APIs, with high confidentiality and integrity impacts due to the changed scope.
The vulnerability is addressed in OpenEMR 8.0.0 via commit fe6341496dc82d5b4f5a3f35891bb2e2481f3b25, as documented in the GitHub security advisory GHSA-2hq8-wc73-jvvq. Affected paths include interface/patient_file/front_payment.php (line 765) and portal/portal_payment.php (line 537). Practitioners should upgrade to version 8.0.0 or later to mitigate exposure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9329
Vulnerability Data
OpenEMR is a free and open source electronic health records and medical practice management application. From 5.0.2 to before 8.0.0, there are (at least) two paths where the gateway_api_key secret value is rendered to the client in plaintext. These secret…
more
keys being leaked could result in arbitrary money movement or broad account takeover of payment gateway APIs. This vulnerability is fixed in 8.0.0.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized actors from obtaining sensitive information.
Information flow enforcement structurally prevents sensitive data from reaching unauthorized recipients.
Protection of information at rest prevents unauthorized exposure of stored sensitive data.
Transmission confidentiality mechanisms stop exposure of sensitive data on the wire.
Least privilege reduces the set of actors who can reach sensitive information.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Suppressing system details, error specifics, and previous log-on information until successful authentication reduces the information an unauthenticated attacker can gather.
Requiring encryption, access controls, and recipient authentication for transfers directly reduces the chance that sensitive data reaches an unauthorized observer.
Secure delivery, protected storage, and confidentiality of allocation records limit exposure of authentication material to unauthorized observers.
A.8.1's policy+enforcement on access controls, storage encryption, malware protection, device registration, remote wipe/lock, physical/logical protections, partitioning, and BYOD separation (plus config enforcement via 8.9) stops most unauthorized exposure of sensitive data from endpoints; named remainder is exposures via error messages, side channels or non-endpoint vectors (see A.8.3 mostly on same CWE).
A.8.10 mandates timely, secure deletion (overwriting, crypto erase, certified disposal, automation per retention policy) of unneeded sensitive information on all media, which directly stops most exposure paths in CWE-200; the bounded remainder is exposure that is not a retention issue at all (e.g. CWE-209 error messages, CWE-203 observable discrepancies, CWE-215 debug code).
data masking (incl. pseudonymization/anonymization) directly limits exposure of sensitive data to unauthorized actors per the purpose and guidance, covering most but not all vectors in CWE-200 (e.g. residual indirect re-identification risks or non-masked exposure paths like error messages remain nameable)
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.