CVE-2026-96173: Payments for Hubtel (WordPress plugin) · Insecure Direct Object Reference
Affects Payments for Hubtel (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.0.2 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% 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:L/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
A fixed version 1.0.2 or later should be applied to address this vulnerability. Since the affected versions are prior to 1.0.2, upgrading to 1.0.2 or newer will remediate the issue. No vendor advisory or patch link was provided, so confirm patch availability from the official plugin source before upgrading.
Description
The Payments for Hubtel WordPress plugin before 1.0.2 does not verify that the requester is authorized to view an order before redirecting a public payment-callback request, allowing unauthenticated attackers to obtain the order key of an arbitrary order and view its contents.