CVE-2026-104338: Razorpay for WooCommerce (WordPress plugin) · Missing Authorization
Affects Razorpay for WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 4.8.9 when convenient.
Data as of 8 Nov 2026, 06:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.8.9
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Upgrade Razorpay for WooCommerce (WordPress plugin) to 4.8.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Razorpay for WooCommerce | Affected
| Fixed in
|
Description
The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not perform an authorization check on one of its REST routes and derives the acting user's identity from an unauthenticated request parameter, allowing an unauthenticated attacker to cause the request to execute as an arbitrary user account for the duration of the request. Exploitation additionally requires a specific coupon Razorpay for WooCommerce WordPress plugin before 4.8.9 to be active on the site.