Payment API key disclosure via client-side rendering
Published Mar 3, 2026 · Updated Mar 3, 2026
Sensitive-data exposure in OpenEMR 5.0.2 and later before 8.0.0 allows remote authenticated users to obtain payment gateway API keys. The front_payment.php and portal_payment.php paths decrypt gateway_api_key and emit it into a client-side apiKey variable for every configured gateway. Payments must be enabled and a key configured; a patient-portal or staff user who reaches a payment page can read the plaintext key and use it for provider-dependent fraud or account takeover.
Summary
What happened
Sensitive-data exposure in OpenEMR 5.0.2 and later before 8.0.0 allows remote authenticated users to obtain payment gateway API keys. The front_payment.php and portal_payment.php paths decrypt gateway_api_key and emit it into a client-side apiKey variable for every configured gateway. Payments must be enabled and a key configured; a patient-portal or staff user who reaches a payment page can read the plaintext key and use it for provider-dependent fraud or account takeover.
The record
- CVE
- CVE-2026-25146
- Published
- Mar 3, 2026
- Updated
- Mar 3, 2026
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-200, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2026CVE publishedPublication date reported by the CVE source.
- Mar 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 5.0.2, < 8.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-2hq8-wc73-jvvq payment-page proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo