PeachPay Plugin up to 1.120.46 on WordPress Configuration peachpay_stripe_handle_admin_actions cross-site request forgery

Summaryinfo

A vulnerability has been found in PeachPay Plugin up to 1.120.46 on WordPress and classified as problematic. The impacted element is the function peachpay_stripe_handle_admin_actions of the component Configuration Handler. The manipulation leads to cross-site request forgery. This vulnerability is listed as CVE-2026-9618. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in PeachPay Plugin up to 1.120.46 on WordPress and classified as problematic. This issue affects the function peachpay_stripe_handle_admin_actions of the component Configuration Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:

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.

The weakness was presented by Benedictus Jovan. The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2026-9618 since 05/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• PeachPay Plugin

Version

• 1.120.0
• 1.120.1
• 1.120.2
• 1.120.3
• 1.120.4
• 1.120.5
• 1.120.6
• 1.120.7
• 1.120.8
• 1.120.9
• 1.120.10
• 1.120.11
• 1.120.12
• 1.120.13
• 1.120.14
• 1.120.15
• 1.120.16
• 1.120.17
• 1.120.18
• 1.120.19
• 1.120.20
• 1.120.21
• 1.120.22
• 1.120.23
• 1.120.24
• 1.120.25
• 1.120.26
• 1.120.27
• 1.120.28
• 1.120.29
• 1.120.30
• 1.120.31
• 1.120.32
• 1.120.33
• 1.120.34
• 1.120.35
• 1.120.36
• 1.120.37
• 1.120.38
• 1.120.39
• 1.120.40
• 1.120.41
• 1.120.42
• 1.120.43
• 1.120.44
• 1.120.45
• 1.120.46

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion