Payments for Hubtel
payments-hubtel · plugin
Known security vulnerabilities for Payments for Hubtel. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
3 exploitable without logging in · latest Oct 1, 2026
Before you install
Use with care
- 3 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.0.3 · last updated Oct 26, 2026 · 90+ installs
wordpress.org status checked on Nov 3, 2026
Vulnerabilities
- High 7.5
CVE-2026-96255unauthenticated→ 1.0.2
Payments for Hubtel < 1.0.2 - Unauthenticated Payment Gateway Credentials Disclosure via Debug Log
- Medium 5.3
CVE-2026-96200unauthenticated→ 1.0.2
Payments for Hubtel < 1.0.2 - Unauthenticated Payment Confirmation Forgery via Delayed Payment Callback
- Medium 5.3
CVE-2026-96173unauthenticated→ 1.0.2
Payments for Hubtel < 1.0.2 - Unauthenticated Order Key Disclosure via IDOR
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).