Rupantorpay: A security weakness
Rupantorpay is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Rupantorpay
- Plugin slug
rupantorpay- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jan 28, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jan 28, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Rupantorpay to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
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 Rupantorpay plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_webhook() function in all versions up to, and including, 2.0.0. This makes it possible for unauthenticated attackers to modify WooCommerce order statuses by sending crafted requests to the WooCommerce API endpoint.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N