The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not sanitize and escape a value derived from an
Source GCVE Database
Not known to be exploited : upgrade to 4.8.9 soon.
Data as of 8 Nov 2026, 08:05 UTC
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.
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
|
AI-suggested
Upgrade the Razorpay for WooCommerce WordPress plugin to version 4.8.9 or later, where this vulnerability has been addressed. No other mitigation guidance is provided, and no indication exists that the vulnerability is mitigated without patching.
Description
The Razorpay for WooCommerce WordPress plugin versions before 4.8.9 contain a vulnerability where a value derived from an incoming webhook request is not properly sanitized or escaped before being used in a SQL query. This flaw allows users who can obtain the webhook secret, typically administrators, to perform SQL injection attacks.