# CVE-2026-39656: Razorpay Razorpay for WooCommerce missing authorization

Source: https://junglewise.ai/threats/cve-2026-39656-razorpay-razorpay-for-woocommerce-missing-authorization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-08. Updated: 2026-07-24  
License: CC BY 4.0 with a link back

CVE-2026-39656 · Severity: medium · CVSS 5.3 · Published 2026-04-08

The Razorpay for WooCommerce plugin, which enables businesses to accept payments on their WordPress websites, contains a security flaw in its access control settings. This vulnerability could allow an unauthorized individual to perform actions that should be restricted to administrators or specific users. While the impact is limited, it could lead to unauthorized changes in the store's configuration or payment processing flow.

Technologies: [Razorpay for WooCommerce](https://junglewise.ai/threats/technologies/razorpay-for-woocommerce). Vendors: [Razorpay](https://junglewise.ai/threats/vendors/razorpay).

## Quick answers

**Is CVE-2026-39656 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-39656 being exploited in the wild.

**How severe is CVE-2026-39656?** Medium severity, with a CVSS score of 5.3, published 8 April 2026.

**Which products and versions are affected?** Razorpay for WooCommerce <= 4.8.3.

**Is there a fix for CVE-2026-39656?** A patch was published on 2026-04-08: Patch available in version 4.8.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-39656 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-39656?** Check whether you run Razorpay for WooCommerce at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A Missing Authorization (CWE-862) vulnerability exists in the Razorpay for WooCommerce plugin (woo-razorpay) through version 4.8.3. The flaw stems from a failure to properly validate user permissions or implement sufficient nonce checks on certain functions, leading to broken access control. An unauthenticated remote attacker can exploit this to execute actions that should require higher privilege levels. The vulnerability is addressed in version 4.8.4. According to the CVSS vector, the primary impact is on integrity (Partial), with no direct impact on confidentiality or availability.

## Affected products

- Razorpay Razorpay for WooCommerce (woo-razorpay) <= 4.8.3

## Timeline

- 2026-01-17: other: Vulnerability reported by Nguyen Ba Khanh
- 2026-02-16: disclosed: Initial disclosure by Patchstack
- 2026-04-08: advisory: CVE published to NVD
- 2026-04-08: patched: Patch available in version 4.8.4

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/Wordpress/Plugin/woo-razorpay/vulnerability/wordpress-razorpay-for-woocommerce-plugin-4-8-2-broken-access-control-vulnerability?_s_id=cve](https://patchstack.com/database/Wordpress/Plugin/woo-razorpay/vulnerability/wordpress-razorpay-for-woocommerce-plugin-4-8-2-broken-access-control-vulnerability?_s_id=cve)

## Related threats

- [Razorpay for WooCommerce SQL injection in webhook handler](https://junglewise.ai/threats/cve-2026-104639-the-razorpay-for-woocommerce-wordpress-plugin-before-4-8-9-does)
- [Razorpay for WooCommerce authorization bypass in REST route](https://junglewise.ai/threats/cve-2026-104338-the-razorpay-for-woocommerce-wordpress-plugin-before-4-8-9-does)
- [Razorpay for WooCommerce order data disclosure](https://junglewise.ai/threats/cve-2026-104337-the-razorpay-for-woocommerce-wordpress-plugin-before-4-8-9-does)
- [Razorpay for WooCommerce authorization bypass in REST API](https://junglewise.ai/threats/cve-2026-104118-the-razorpay-for-woocommerce-wordpress-plugin-before-4-8-8-does)