# CVE-2026-104338: Razorpay for WooCommerce authorization bypass in REST route

Source: https://junglewise.ai/threats/cve-2026-104338-the-razorpay-for-woocommerce-wordpress-plugin-before-4-8-9-does  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-104338 · Severity: info · Published 2026-11-08

Razorpay for WooCommerce is a WordPress payment plugin that integrates the Razorpay payment gateway with online stores. An unauthenticated attacker can bypass authorization checks on a REST API endpoint and impersonate any user account, provided a specific coupon plugin is active on the site. This could allow unauthorized access to orders, customer data, or store functionality under a victim's account.

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-104338 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-104338 being exploited in the wild.

**How severe is CVE-2026-104338?** Informational severity, published 8 November 2026.

**Which products and versions are affected?** Razorpay for WooCommerce before 4.8.9.

**Is there a fix for CVE-2026-104338?** Yes: fixed in 4.8.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-104338 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-104338?** 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.

## How to fix

- Fixed in 4.8.9

## Technical details

The plugin's REST route lacks proper authorization validation and derives the acting user's identity from an unauthenticated request parameter, enabling user context switching without authentication. Exploitation requires an attacker to send a crafted request to the vulnerable REST endpoint while a specific coupon plugin is active on the site; the attack succeeds against any user account for the duration of that request. A fix is available in version 4.8.9 and later.

## Affected products

- Razorpay Razorpay for WooCommerce before 4.8.9

## Timeline

- 2026-11-06: disclosed
- 2026-11-08: advisory

## References

- [https://wpscan.com/vulnerability/7a414b2d-ee06-448a-a83d-3bfd5db66528/](https://wpscan.com/vulnerability/7a414b2d-ee06-448a-a83d-3bfd5db66528/)

## 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 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)
- [Razorpay Razorpay for WooCommerce missing authorization](https://junglewise.ai/threats/cve-2026-39656-razorpay-razorpay-for-woocommerce-missing-authorization)