Payments for Hubtel: Public payment callback exposes order keys and contents
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. The authoritative export does not name the request parameter or handler beyond the affected feature described above. The authoritative export identifies the fixed release as 1.0.2.
- Component
- Payments for Hubtel
- Plugin slug
payments-for-hubtel- Affected
- < 1.0.2
- Safe version
1.0.2- Published
- Oct 01, 2026
- Weakness
- Not assigned
This CVE was published Oct 01, 2026 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update Payments for Hubtel to 1.0.2 or a later supported release. Authorize access to the target order before redirecting or returning its key; do not treat a caller-supplied order identifier as proof of ownership.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.