How broadly exploitable is this vulnerability?

Exploitability depends on who can access the affected views or endpoints. Any party that can legitimately or illegitimately access the application pages where the `gateway_api_key` is rendered can potentially harvest the keys. This includes compromised user accounts, malicious insiders, or attackers with network visibility if traffic is not properly encrypted.

What level of access does an attacker need?

Typically, the attacker needs at least the same level of access as a user or administrator who can reach the pages or APIs that contain the exposed key. In some deployments, this might require authenticated access; in others, misconfigurations could make the paths more broadly reachable. Once the key is obtained, the attacker no longer needs access to OpenEMR itself to abuse the payment gateway APIs.

What is the safest general fix pattern?

The safest approach is to ensure that payment gateway secrets are never returned in responses or rendered in any client-visible context. Secrets should be stored in dedicated secret storage and only used server-side to call payment APIs. Any administrative UI should display only non-sensitive metadata, with options to rotate or re-enter secrets rather than view them.

Severity:

CRITICAL RISK

(9.6)

Sensitive Information Exposure (CWE-200) of Payment Gateway API Keys in OpenEMR

CVE-2026-25146

Published:

Mar 3, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Sensitive Information Exposure

CWE:

CWE-200

Impact:

Payment Gateway Account Compromise and Fraudulent Transactions

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Vulnerability Type

Category:

Sensitive Information Exposure

CWE:

CWE-200

Impact:

Payment Gateway Account Compromise and Fraudulent Transactions

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Sensitive Information Exposure (CWE-200) of Payment Gateway API Keys in OpenEMR

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare