PeachPay <= 1.120.46 - Cross-Site Request Forgery to Stripe Unlink
Strategic Overview
- Status
- Patched in 1.120.47
- Affected Plugin
- PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
- Affected Version
<= 1.120.46- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-9618
At a glance
CVE-2026-9618 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the PeachPay WordPress plugin, affecting versions <= 1.120.46. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.120.47; sites on affected versions should update now. Disclosed May 2026, reported by Benedictus Jovan (aillesiM).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in PeachPay <= 1.120.46 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For PeachPay the fix is 1.120.47: builds <= 1.120.46 are affected, anything from 1.120.47 onward is not.
Remediation
Update to version 1.120.47, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to PeachPay: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PeachPay 1.120.47 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
- 6.5CVE-2025-9463: Payments Plugin and Checkout… SQL Injection
CVE-2025-9463 - 6.1CVE-2024-11362: Payments Plugin and Checkout… Reflected XSS
CVE-2024-11362 - 5.3CVE-2025-14978: PeachPay Unauthenticated Order Status Modification
CVE-2025-14978 - 5.3CVE-2025-58634: PeachPay Payments <= 1.117.4 Missing Authorization
CVE-2025-58634
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C