CVE-2026-9618: CWE-352 Cross-Site Request Forgery (CSRF) in peachpay PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
The PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.120.46. This is due to missing or incorrect nonce validation on the peachpay_stripe_handle_admin_actions function. This makes it possible for unauthenticated attackers to permanently delete all stored Stripe credentials — including publishable keys, secret keys, webhook secrets, and Apple Pay configuration — from the WordPress database, disabling Stripe payment processing for the store via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
The PeachPay plugin for WooCommerce suffers from a CSRF vulnerability due to improper nonce validation in the peachpay_stripe_handle_admin_actions function. This flaw allows unauthenticated attackers to forge requests that can delete all Stripe-related credentials stored in the WordPress database, including publishable keys, secret keys, webhook secrets, and Apple Pay configuration. Exploitation requires tricking an administrator into performing an action such as clicking a crafted link. This disrupts Stripe payment processing functionality for the affected WooCommerce store. The vulnerability affects all plugin versions up to 1.120.46. No patch or official fix has been disclosed as of the publication date.
Potential Impact
Successful exploitation results in the permanent deletion of Stripe credentials from the WordPress database, disabling Stripe payment processing for the affected WooCommerce store. This impacts the integrity and availability of payment processing but does not directly disclose sensitive data or cause system compromise beyond payment disruption.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on untrusted links while logged into the WordPress admin interface and consider implementing additional CSRF protections or monitoring for suspicious admin actions related to Stripe credentials.
CVE-2026-9618: CWE-352 Cross-Site Request Forgery (CSRF) in peachpay PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
Description
The PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.120.46. This is due to missing or incorrect nonce validation on the peachpay_stripe_handle_admin_actions function. This makes it possible for unauthenticated attackers to permanently delete all stored Stripe credentials — including publishable keys, secret keys, webhook secrets, and Apple Pay configuration — from the WordPress database, disabling Stripe payment processing for the store via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS v3.1
Score 4.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The PeachPay plugin for WooCommerce suffers from a CSRF vulnerability due to improper nonce validation in the peachpay_stripe_handle_admin_actions function. This flaw allows unauthenticated attackers to forge requests that can delete all Stripe-related credentials stored in the WordPress database, including publishable keys, secret keys, webhook secrets, and Apple Pay configuration. Exploitation requires tricking an administrator into performing an action such as clicking a crafted link. This disrupts Stripe payment processing functionality for the affected WooCommerce store. The vulnerability affects all plugin versions up to 1.120.46. No patch or official fix has been disclosed as of the publication date.
Potential Impact
Successful exploitation results in the permanent deletion of Stripe credentials from the WordPress database, disabling Stripe payment processing for the affected WooCommerce store. This impacts the integrity and availability of payment processing but does not directly disclose sensitive data or cause system compromise beyond payment disruption.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on untrusted links while logged into the WordPress admin interface and consider implementing additional CSRF protections or monitoring for suspicious admin actions related to Stripe credentials.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-26T16:40:10.234Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a17efcfe29bf47b50bb75fb
Added to database: 5/28/2026, 7:33:35 AM
Last enriched: 5/28/2026, 7:48:58 AM
Last updated: 5/29/2026, 12:36:44 PM
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.