# CVE-2026-104118: Razorpay for WooCommerce authorization bypass in REST API

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

CVE-2026-104118 · Severity: medium · CVSS 5.3 · Published 2026-10-04

The Razorpay for WooCommerce plugin, which handles payment processing for online stores, fails to verify that an attacker has permission to modify an order before allowing changes through its REST API. An unauthenticated attacker can modify shipping information on any customer's order without authentication, potentially redirecting or intercepting customer shipments and exposing order details.

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

**How severe is CVE-2026-104118?** Medium severity, with a CVSS score of 5.3, published 4 October 2026.

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

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

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

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

## Technical details

The vulnerability is an insecure direct object reference (IDOR) in a REST API endpoint used during checkout. The plugin fails to perform ownership or authorization checks before allowing modifications to shipping information on orders. An unauthenticated attacker can exploit this by directly calling the REST API route with arbitrary order identifiers to modify shipping details on any order in the system.

## Affected products

- Razorpay Razorpay for WooCommerce before 4.8.8

## Timeline

- 2026-10-02: disclosed
- 2026-10-02: patched: Fix released in version 4.8.8

## References

- [https://wpscan.com/vulnerability/d94ebc87-c404-4b30-8291-26c4bc2eb63b/](https://wpscan.com/vulnerability/d94ebc87-c404-4b30-8291-26c4bc2eb63b/)

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