CVE-2026-9618 json
PeachPay <= 1.120.46 - Cross-Site Request Forgery to Stripe Unlink
published 2026-05-28 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-32731
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- peachpay PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/2270b66f-b07c-44ce-b161-7b2123f8c21e?source=cve
- plugins.trac.wordpress.org /browser/peachpay-for-woocommerce/tags/1.120.45/core/payments/stripe/functions.php#L612
- plugins.trac.wordpress.org /browser/peachpay-for-woocommerce/tags/1.120.45/core/payments/stripe/functions.php#L640
- plugins.trac.wordpress.org /browser/peachpay-for-woocommerce/tags/1.120.45/core/admin/settings.php#L190
- plugins.trac.wordpress.org /browser/peachpay-for-woocommerce/tags/1.120.23/core/payments/stripe/functions.php#L612
- plugins.trac.wordpress.org /browser/peachpay-for-woocommerce/tags/1.120.23/core/payments/stripe/functions.php#L640
- plugins.trac.wordpress.org /browser/peachpay-for-woocommerce/tags/1.120.23/core/admin/settings.php#L190
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3550723%40peachpay-for-woocommerce&new=3550723%40peachpay-for-w
Sources
- CVE List CVE-2026-9618
- NVD CVE-2026-9618
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.