CVE-2026-96255: Payments for Hubtel (WordPress plugin) · Information Exposure
Affects Payments for Hubtel (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.0.2 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Payments for Hubtel (WordPress plugin) to 1.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Payments for Hubtel | Affected
| Fixed in
|
AI-suggested
The vulnerability affects versions prior to 1.0.2. Users should upgrade to version 1.0.2 or later once available to remediate this issue. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for the official fix or updates. Until patched, restrict public access to debug logs and avoid enabling debug logging in production environments.
Description
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.