Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2026-25146 β€” AI Deep Analysis Summary

CVSS 9.6 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: OpenEMR leaks the `gateway_api_key` in plaintext to the client.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **CWE**: CWE-200 (Information Exposure). πŸ” **Flaw**: The application fails to mask the API key in at least two specific code paths, sending it directly to the frontend in clear text. πŸ“

Q3Who is affected? (Versions/Components)

πŸ₯ **Vendor**: OpenEMR (Open Source Medical System). πŸ“¦ **Affected Versions**: Versions 5.0.2 through 8.0.0 (prior to the fix). ⚠️ Check your deployment version immediately! πŸ“…

Q4What can hackers do? (Privileges/Data)

πŸ’» **Privileges**: Requires Low Privilege (PR:L). πŸ•΅οΈ **Data Access**: Hackers can retrieve the `gateway_api_key`. 🎯 **Impact**: Full compromise of payment gateway accounts, enabling financial fraud and data theft. πŸ’³

Q5Is exploitation threshold high? (Auth/Config)

βš–οΈ **Threshold**: Low. πŸ“Ά **Network**: Network Accessible (AV:N). πŸ”‘ **Auth**: Requires Low Privileges (PR:L) - meaning a basic authenticated user can exploit this. πŸšͺ No User Interaction needed (UI:N). πŸš€

Q6Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exp**: No public PoC or Exploit code provided in the data. πŸ“„ **References**: Only GitHub commit links and security advisories are available. πŸ”’ Stay vigilant but no ready-made scripts exist yet. πŸ›‘

Q7How to self-check? (Features/Scanning)

πŸ” **Check**: Inspect network traffic for plaintext `gateway_api_key` in responses. πŸ“‚ **Code Scan**: Look at `interface/patient_file/front_payment.php` (Line 765) and `portal/portal_payment.php` (Line 537).…

Q8Is it fixed officially? (Patch/Mitigation)

βœ… **Fixed**: Yes! A fix is available via GitHub commit `fe6341496dc82d5b4f5a3f35891bb2e2481f3b25`. πŸ› οΈ **Action**: Update to the latest version or apply the specific patch referenced in the GHSA advisory. πŸ”„

Q9What if no patch? (Workaround)

🚧 **Workaround**: If patching is delayed, restrict access to payment-related endpoints. πŸ”’ **Mitigation**: Implement strict WAF rules to block requests attempting to extract API keys.…

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Priority**: HIGH. 🚨 **Reason**: CVSS Score indicates High Confidentiality and Integrity impact. πŸ’° Financial data is at stake.…