WooCommerce Stripe Payment Gateway <= 10.7.0 — Missing Authorization to Unauthenticated Order Status Manipulation via 'order' Parameter
CVE-2026-2381Published · Updated Action summary
Affected: ≤10.7.0Update to 10.8.0 or newer
All remediation steps- Severity
- Medium6.5
- CVSS
- 6.5CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:LAvailability- Low
- Weakness
- CWE-862 Missing Authorization
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
WooCommerce Stripe Payment Gateway woocommerce-gateway-stripe
- Affected≤ 10.7.0
- Patched in10.8.0
Update to 10.8.0 or newer.
You are affected if you run ≤ 10.7.0. Version 10.8.0 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WooCommerce Stripe Payment Gateway.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 10.8.0, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch WooCommerce Stripe Payment Gateway to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Dmitrii Ignatyev.
The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `ajax_pay_for_order()` function in all versions up to, and including, 10.7.0 This is due to a missing order ownership or order_key verification when processing payment for an order via the `wc_stripe_pay_for_order` WC-AJAX endpoint. The function only validates a nonce (which is publicly available on any WooCommerce page where Express Checkout is enabled), but does not verify that the requesting user owns the target order and is allowed to modify it. This makes it possible for unauthenticated attackers to force any pending order into a failed status by providing a fake payment method, causing a payment exception that updates the order status to "failed" via sequential order ID enumeration.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in WooCommerce Stripe Payment Gateway
All 6| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | 11.0.1 - Insecure Storage of Password 10.9.0 – 11.0.1Update to 11.1.0 | CVE-2026-123145 | |
| Medium6.5 | Insecure Direct Object Reference via update_payment_intent_ajax ≤7.6.1Update to 7.6.2 | CVE-2023-51502 | |
| Medium5.4 | Cross-Site Request Forgery <7.6.1Update to 7.6.1 | CVE-2023-44999 | |
| Medium6.3 | Missing Authorization ≤7.4.0Update to 7.4.1 | CVE-2023-35049 | |
| High7.5 | Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure ≤7.4.0Update to 5.5.1 or 5.6.3 or 5.7.1 or 5.8.2 or 5.9.1 or 6.0.1 or 6.1.1 or 6.2.1 or 6.3.1 or 6.4.4 or 6.5.2 or 6.6.1 or 6.7.1 or 6.8.1 or 6.9.1 or 7.0.3 or 7.1.1 or 7.2.1 or 7.3.1 or 7.4.1 | CVE-2023-34000 |
- Medium4.311.0.1 - Insecure Storage of Password
10.9.0 – 11.0.1Update to 11.1.0
- Medium6.5Insecure Direct Object Reference via update_payment_intent_ajax
≤7.6.1Update to 7.6.2
- Medium5.4Cross-Site Request Forgery
<7.6.1Update to 7.6.1
- Medium6.3Missing Authorization
≤7.4.0Update to 7.4.1
- High7.5Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure
≤7.4.0Update to 5.5.1 or 5.6.3 or 5.7.1 or 5.8.2 or 5.9.1 or 6.0.1 or 6.1.1 or 6.2.1 or 6.3.1 or 6.4.4 or 6.5.2 or 6.6.1 or 6.7.1 or 6.8.1 or 6.9.1 or 7.0.3 or 7.1.1 or 7.2.1 or 7.3.1 or 7.4.1
Same weakness (Missing Authorization)
All Missing Authorization| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header | CVE-2026-120688 | |
| Critical9.8 | Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission | CVE-2026-125055 | |
| Critical9.8 | Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter | CVE-2026-119077 | |
| Medium5.3 | Unauthenticated Sensitive Information Exposure in 'search' Parameter | CVE-2026-121518 |
- High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup
≤5.25.25Update to 5.26.45
- Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder
≤1.0.2Update to 1.1
- Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System
≤3.3.9Update to 3.4.0
- Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce
≤5.127.0Update to 5.128.0
Timeline
CVE published
Severity medium, CVSS 6.5
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.