CVE-2026-104118: Razorpay for WooCommerce (WordPress plugin) · Insecure Direct Object Reference
Affects Razorpay for WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.8.8 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.8.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Oct 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 16 Nov 2026.
What to do
Upgrade Razorpay for WooCommerce (WordPress plugin) to 4.8.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Razorpay for WooCommerce | Affected
| Fixed in
|
AI-suggested
A fix is available in Razorpay for WooCommerce version 4.8.8. Users should upgrade to version 4.8.8 or later to remediate this authorization bypass vulnerability.
Description
A vulnerability in the Razorpay for WooCommerce WordPress plugin before version 4.8.8 allows unauthenticated attackers to modify shipping information on arbitrary orders via a REST API route that lacks proper ownership or authorization checks.