Razorpay for WooCommerce < 4.8.9 - Unauthenticated User Context Switch via 1cc Coupon Route
- Exploited
- No known exploitation
- Fix
- Fixed in 4.8.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.8.9.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.14% · 3rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Razorpay for WooCommerce WordPress plugin, a payment add-on for WooCommerce stores, can be abused by an unauthenticated attacker to make a request run as any user account for its duration. The flaw is in a REST route that lacks an authorization check and takes the acting user from an unauthenticated request parameter, and it only works when a specific coupon is active on the site.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.7/10CVSS 3.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.8.9.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Razorpay for WooCommerce
fixed in 4.8.9
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-104338
Is CVE-2026-104338 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-104338?
Razorpay for WooCommerce: before 4.8.9.Source: cve.now feed data
How do I fix CVE-2026-104338?
Upgrade to a fixed version: 4.8.9.Source: cve.now feed data