Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCreate low-value PayPal order
-
DeliveryObtain approved uncaptured PayPal token
-
ExploitAdd high-value items to WooCommerce cart
-
InstallInitiate checkout as guest
-
C2Submit foreign PayPal token on order-received endpoint
-
ExecutePlugin marks order paid
-
ImpactSubscription or goods obtained without payment
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Data authenticity verification
|
| Exploitation Conditions | The plugin must be using PayPal as the active payment gateway for WooCommerce, and the Subscriptions for WooCommerce plugin version must be below 2.0.1. For unauthenticated exploitation, WooCommerce guest checkout must be enabled (a common default configuration for many stores). If guest checkout is disabled, the attacker must possess a registered WooCommerce customer account (PR:L equivalent). In all cases, the attacker must independently obtain a valid PayPal order token with an approved but uncaptured status - for example, by initiating a separate low-value PayPal transaction through their own account. There is no requirement for network proximity, special system privileges, or user interaction from the victim merchant. Exploitation is limited to stores running both WooCommerce and this specific subscription plugin with PayPal enabled; stores using only other payment gateways (Stripe, direct bank, etc.) are not affected. |
| Impact | The NVD CVSS 3.1 score of 5.9 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N reflects that, while the attack is network-accessible and requires no authentication (when guest checkout is enabled), the attacker must independently possess a valid approved but uncaptured PayPal order token - raising attack complexity to High. Despite the medium CVSS, the real-world business impact is potentially severe: exploitation results in direct financial loss to merchants for every fraudulently completed order, and the attack is fully automated once a valid token is obtained. A publicly available proof-of-concept (per WPScan) significantly lowers the practical barrier, even for the token-sourcing step. No EPSS score was provided in the input data, so probability-of-exploitation-in-the-wild cannot be quantified from this dataset. The vulnerability is absent from the CISA KEV catalog, suggesting no confirmed mass exploitation at time of analysis, but the public POC and straightforward business logic nature make opportunistic fraud realistic. The 'Information Disclosure' tag in the source intelligence appears to be a mislabeling - the actual impact is financial integrity bypass with no confidentiality dimension, consistent with the CVSS C:N rating. WooCommerce subscription plugins are attractive targets for fraud, elevating priority beyond what raw CVSS alone indicates for affected merchants. |
| Exploit ScenarioDerived | An attacker creates a minimal PayPal order - for example, a one-cent transaction - through their own PayPal account and obtains the resulting approved-but-uncaptured order token. They then add expensive items (e.g., a high-value subscription product) to the WooCommerce store, proceed to checkout as a guest, and on the order-received page inject the pre-obtained PayPal token in place of the token that would correspond to the actual order value. The plugin captures the supplied token, receives a COMPLETED status, and marks the full-price WooCommerce order as paid - granting subscription access or triggering fulfillment without the attacker paying the actual order total. A public POC is available, meaning the token substitution technique is documented and reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 07, 2026
Payment integrity bypass in the Subscriptions for WooCommerce plugin (versions before 2.0.1) enables financial fraud by allowing substitution of an arbitrary approved PayPal order token during the WooCommerce order-received flow. The plugin captures a client-supplied token and marks any order paid solely based on a COMPLETED capture status, without verifying that the captured amount matches the order total or that the token belongs to the specific order. Unauthenticated attackers - where guest checkout is enabled - can exploit this to obtain goods or subscription access without paying the actual order price. A publicly available proof-of-concept exists; no CISA KEV listing at time of analysis.
RemediationAI
Update the Subscriptions for WooCommerce plugin to version 2.0.1 or later immediately, as this version introduces proper server-side validation binding the PayPal order token to the specific WooCommerce order and verifying the captured amount against the order total. The patch is confirmed available per the WPScan advisory at https://wpscan.com/vulnerability/0653ccce-5427-4ffc-a34c-18b45710d9f3/. As a compensating control prior to patching, merchants can disable PayPal as a payment method for new orders - this eliminates the attack surface entirely but prevents legitimate PayPal payments, so weigh against revenue impact. Alternatively, disabling guest checkout reduces the unauthenticated attack surface to registered customer accounts only, though authenticated exploitation remains possible. Merchants should audit order history for discrepancies between order totals and captured PayPal amounts to identify potential prior fraud, particularly for high-value subscription or product orders marked as paid via PayPal in recent weeks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the PayPal payment capture integration of the Subscriptions for WooCommerce WordPress plugin (CPE: cpe:2.3:a:unknown:subscriptions_for_woocommerce:*:*:*:*:*:*:*:*). The WooCommerce order-received flow is designed to finalize orders after a payment gateway confirms completion; however, the plugin fails to implement two essential binding checks: it does not validate that the captured PayPal order amount equals the WooCommerce order total, and it does not verify that the PayPal order token was originally created for the specific WooCommerce order being completed. The plugin trusts the client-supplied token and the gateway's COMPLETED capture status signal as sufficient proof of full payment. Although CWE was not assigned by the reporter, this is a classic business logic flaw - analogous to CWE-345 (Insufficient Verification of Data Authenticity) and CWE-20 (Improper Input Validation) - where server-side state is derived from an untrusted client parameter without cross-referencing authoritative order metadata. The flaw sits at the intersection of PayPal's token-based flow and WooCommerce's order-received webhook/redirect handling.
Know when Subscriptions For Woocommerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Network vector and no auth required when guest checkout enabled; AC:H for mandatory pre-obtained valid PayPal token; I:H for complete payment integrity bypass; C and A not impacted.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Subscriptions for WooCommerce WordPress plugin before 2.0.1 does not validate the payment amount or bind the PayPal order token to the order being completed on the WooCommerce order-received flow: it captures a client-supplied token and marks the order paid whenever the capture status is COMPLETED, without comparing the captured amount to the order total. This allows an attacker (unauthenticated where guest checkout is enabled) to substitute an approved, uncaptured PayPal order token and have an expensive order marked paid without paying its price.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote code execution in Subscriptions for WooCommerce WordPress plugin (before 2.0.1) is reachable by any authenticated
Unauthenticated remote attackers can retrieve a WooCommerce store's complete subscription roster - customer usernames, p
Privilege escalation in the Subscriptions for WooCommerce WordPress plugin (versions up to and including 2.0.0) allows a
Cross-site request forgery in the WordPress plugin Subscriptions for WooCommerce before 2.0.3 allows an attacker to canc
Insecure Direct Object Reference (IDOR) in the Subscriptions for WooCommerce WordPress plugin before 2.0.1 allows any au
An authentication bypass vulnerability exists in WP Swings Subscriptions for WooCommerce plugin versions up to and inclu
Arbitrary plugin installation in the WP Swings Subscriptions for WooCommerce plugin (versions up to and including 2.0.0)
The Subscriptions for WooCommerce plugin contains a critical authentication bypass vulnerability in the subscription can
EUVD-2026-54400
GHSA-p384-7c3j-gqm7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB