CVE-2026-97299: Razorpay Payment Links for WooCommerce unauthenticated CSRF

CVE-2026-97299 · Severity: medium · CVSS 5.4 · Published 2026-09-30

The Razorpay Payment Links plugin for WooCommerce allows attackers to trick authenticated users into performing unwanted payment actions through crafted web pages. An attacker can exploit this to initiate unauthorized payment transactions without the user's knowledge or consent, potentially resulting in fraudulent charges.

Vendors: Razorpay.

Quick answers

Is CVE-2026-97299 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-97299 being exploited in the wild.
How severe is CVE-2026-97299?
Medium severity, with a CVSS score of 5.4, published 30 September 2026.
Which products and versions are affected?
Razorpay Payment Links for WooCommerce up to 2.1.5.
Is there a fix for CVE-2026-97299?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-97299 attacked?
It is attacked over the network.
Am I affected by CVE-2026-97299?
Check whether you run Razorpay Payment Links 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.

Technical details

This is a Cross-Site Request Forgery (CSRF) vulnerability in the plugin's payment link handling that permits unauthenticated requests to trigger payment operations. The vulnerability affects versions up to 2.1.5 and allows an attacker to craft malicious requests that, when visited by a logged-in user, execute unintended payment transactions. No precondition of special privileges is required beyond the user being authenticated to the WordPress/WooCommerce installation.

Affected products

  • Razorpay Payment Links for WooCommerce up to 2.1.5

Timeline

  • 2026-09-30: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.