CVE-2026-104338 · Package
NO FIX YET · SEE WHAT TO DO
The Razorpay for WooCommerce WordPress plugin takes the acting user's identity from an unauthenticated request parameter on one REST route, with no authorization check. An unauthenticated attacker can make a request run as an arbitrary user account for the duration of that request, but only while a specific coupon is active on the site.
first public Nov 8, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Razorpay for WooCommerce WordPress plugin before 4.8.9 are exposed, and only while a specific coupon is active. Sites without the plugin, or on 4.8.9 or later, are not affected. The sources do not say which coupon is involved.
Not affected if coupon-inactive, plugin-4.8.9-or-later
Who cares razorpay, self-hosted, woocommerce, wordpress
4.8.9.4.8.9 or later.The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not perform an authorization check on one of its REST routes and derives the acting user's identity from an unauthenticated request parameter, allowing an unauthenticated attacker to cause the request to execute as an arbitrary user account for the duration of the request. Exploitation additionally requires a specific coupon Razorpay for WooCommerce WordPress plugin before 4.8.9 to be active on the site.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.