Skip to main content
VulnerabilityPublished Updated

CVE-2026-104118: Razorpay for WooCommerce (WordPress plugin) · Insecure Direct Object Reference

Affects Razorpay for WooCommerce (WordPress plugin)Source CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Razorpay for WooCommerceAffected
  • <4.8.8
Fixed in
  • 4.8.8

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.

References

Community reviews

Loading reviews…