CVE-2026-9618
Received Received - Intake
Cross-Site Request Forgery in PeachPay WooCommerce Plugin

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: Wordfence

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-06-17
AI Q&A
2026-05-28
EPSS Evaluated
2026-06-16
NVD
CVE-2026-9618
EUVD
EUVD-2026-32731
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
peachpay payments_and_express_checkout_for_woocommerce to 1.120.46 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The vulnerability exists in the PeachPay — Payments & Express Checkout for WooCommerce plugin for WordPress, specifically in all versions up to and including 1.120.46.

It is a Cross-Site Request Forgery (CSRF) vulnerability caused by missing or incorrect nonce validation in the peachpay_stripe_handle_admin_actions function.

This flaw allows unauthenticated attackers to trick a site administrator into performing an action, such as clicking a malicious link, which then causes the permanent deletion of all stored Stripe credentials from the WordPress database.

These credentials include publishable keys, secret keys, webhook secrets, and Apple Pay configuration.

Impact Analysis

If exploited, this vulnerability can permanently delete all stored Stripe credentials from your WordPress database.

As a result, Stripe payment processing for your WooCommerce store will be disabled.

This disruption can lead to loss of payment functionality, potentially causing revenue loss and customer dissatisfaction.

Mitigation Strategies

The vulnerability exists in all versions up to and including 1.120.46 of the PeachPay plugin for WooCommerce. To mitigate this vulnerability, you should update the PeachPay plugin to a version later than 1.120.46 where the nonce validation issue in the peachpay_stripe_handle_admin_actions function is fixed.

Additionally, as a precaution, review and reset any stored Stripe credentials (publishable keys, secret keys, webhook secrets, and Apple Pay configuration) in your WordPress database to ensure no unauthorized deletion has occurred.

Also, educate site administrators to avoid clicking on suspicious links that could trigger forged requests.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9618. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart