What the vulnerability does
01Description
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.
Explanation of Vulnerability in Simple Terms
02Summary
PeachPay for WooCommerce versions up to 1.120.46 are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the payment plugin without their knowledge. The vulnerability requires user interaction and does not expose sensitive data, but can result in unauthorized changes to payment settings.
What an attacker can do
03Attacker Capabilities
Trick a logged-in admin into visiting a malicious page that performs unwanted actions on PeachPay settings.
Potential impact on your site
04Site Impact
An attacker could modify payment configuration, redirect transactions, or alter checkout behavior if an admin visits a malicious link.
Conditions required to exploit
05Prerequisites
Admin must be logged in and visit an attacker-controlled webpage; no special privileges or authentication bypass needed.
Key dates
06Disclosure timeline
May 28, 2026
CVE published
May 28, 2026
Record updated
