CVE-2026-104338VulnerabilityPublished 8 Nov 2026

The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not perform an authorization check on one of its REST

Source GCVE Database

Compare

Authoritative record:CVE-2026-104338· High

Not known to be exploited : upgrade to 4.8.9 soon.

Data as of 8 Nov 2026, 08:05 UTC

Severity

High

Rated High by Threat Radar's AI analysis · 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3g9w-x4v7-974v

What to do

Upgrade Razorpay for WooCommerce (WordPress plugin) to 4.8.9.

Affected software

Product	Affected	Fixed in
Razorpay for WooCommerce	Affected <4.8.9	Fixed in 4.8.9

AI-suggested

A fixed version 4.8.9 or later should be applied to address this vulnerability. Since the plugin version before 4.8.9 is affected, upgrading to 4.8.9 or newer is recommended. No vendor advisory or patch link is provided in the input, so confirm patch availability from the official plugin source before deployment.

Description

The Razorpay for WooCommerce WordPress plugin versions prior to 4.8.9 contain a vulnerability where one of its REST routes lacks proper authorization checks. This flaw allows an unauthenticated attacker to impersonate an arbitrary user account for the duration of the request by manipulating an unauthenticated request parameter. Exploitation requires the presence of a specific coupon feature in the plugin.

Impact

An unauthenticated attacker can perform actions on the site with the privileges of an arbitrary user account for the duration of the REST request. This could lead to unauthorized actions depending on the permissions of the impersonated user. The impact is limited to the scope of the REST route and the active coupon feature requirement.

Summary

The vulnerability in Razorpay for WooCommerce WordPress plugin before version 4.8.9 involves missing authorization validation on a REST API route. The plugin incorrectly derives the acting user's identity from an unauthenticated request parameter, enabling an unauthenticated attacker to execute requests as any user temporarily. Successful exploitation depends on the specific coupon functionality being active on the affected site. No CVSS score or detailed impact metrics are provided, and no known exploits in the wild have been reported.

References

Community reviews

Loading reviews…