Quick answers
- Is CVE-2026-104639 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104639 being exploited in the wild.
- How severe is CVE-2026-104639?
- Informational severity, published 8 November 2026.
- Which products and versions are affected?
- Razorpay for WooCommerce before 4.8.9.
- Is there a fix for CVE-2026-104639?
- Yes: fixed in 4.8.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104639 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-104639?
- Check whether you run Razorpay for WooCommerce at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.8.9
Technical details
The plugin fails to sanitize and escape webhook request parameters before incorporating them into SQL queries, allowing SQL injection. The vulnerability requires knowledge of the webhook secret, typically accessible only to administrators. An attacker can bypass normal authentication controls by directly triggering the webhook endpoint with a crafted payload.
Affected products
- Razorpay Razorpay for WooCommerce before 4.8.9
Timeline
- 2026-11-06: disclosed
- 2026-11-08: advisory