Razorpay for WooCommerce: A security weakness
Razorpay for WooCommerce is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 4.8.2.
- Component
- Razorpay for WooCommerce
- Plugin slug
woo-razorpay- Affected
- <= 4.8.2
- Safe version
> 4.8.2- Published
- Apr 08, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Apr 08, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Razorpay for WooCommerce to a release after 4.8.2, or disable and remove it until a fixed version is available.
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
Missing Authorization vulnerability in Razorpay Razorpay for WooCommerce woo-razorpay allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Razorpay for WooCommerce: from n/a through <= 4.8.2.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N