Accept Stripe Payments < 2.1.4 - Unauthenticated Product Substitution via IDOR
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-639.
Summary
The Accept Stripe Payments WordPress plugin before 2.1.4 does not verify that the product fulfilled when a checkout is completed matches the product the authoritative payment was actually made for, checking only that the amount paid is at least the referenced product's price, allowing unauthenticated attackers who complete a genuine payment to obtain fulfilment for a different, equal- or lower-priced product than the one they paid for.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Accept Stripe Payments | before 2.1.4 | 2.1.4 | Patch available | CNA |
- Accept Stripe Payments VendorUnknown Affected before 2.1.4 Fixed in 2.1.4 Patch available CNA
Remediation
- Fix · CNA Accept Stripe Payments (Unknown) Fixed in 2.1.4
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Accept Stripe Payments 2.1.4
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2026-56199 Accept Stripe Payments < 2.1.4 - Open Redirect via IPN HandlerPriority LOW 20
Timeline
- 2026-10-02 Threatist record created from CVE-2026-81424
- 2026-10-03 Alias added: GHSA-4qcx-xfr8-6hf6
References
Sources
- CVE-2026-81424 · CVE Program
- CVE-2026-81424 · NVD
- FIRST EPSS
- GHSA-4qcx-xfr8-6hf6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences