Payments for Hubtel < 1.0.2 - Unauthenticated Payment Gateway Credentials Disclosure via Debug Log
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-200.
Summary
The Payments for Hubtel WordPress plugin before 1.0.2 does not prevent public access to a debug log in which it records payment requests, including the store's payment gateway API credentials in plain text, allowing unauthenticated attackers to obtain those credentials.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Payments for Hubtel | before 1.0.2 | 1.0.2 | Patch available | CNA |
- Payments for Hubtel VendorUnknown Affected before 1.0.2 Fixed in 1.0.2 Patch available CNA
Remediation
- Fix · CNA Payments for Hubtel (Unknown) Fixed in 1.0.2
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Payments for Hubtel 1.0.2
3 records Highest priority Priority LOW 3 LOW
Other records, highest priority first
- TI-2026-63732 Payments for Hubtel < 1.0.2 - Unauthenticated Payment Confirmation Forgery via Delayed Payment CallbackPriority LOW 29
- TI-2026-63731 Payments for Hubtel < 1.0.2 - Unauthenticated Order Key Disclosure via IDORPriority LOW 29
Timeline
- 2026-10-02 Threatist record created from CVE-2026-96255
- 2026-10-03 Alias added: GHSA-gv9c-r7rv-4q3q
References
Sources
- CVE-2026-96255 · CVE Program
- CVE-2026-96255 · NVD
- FIRST EPSS
- GHSA-gv9c-r7rv-4q3q · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences