CVE-2026-9618Network attack vector

Payment disruption via forged Stripe unlink request

Published May 28, 2026 · Updated May 28, 2026

CSRF in PeachPay Payments & Express Checkout for WooCommerce 1.120.46 and earlier allows remote attackers to delete Stripe credentials. The peachpay_stripe_handle_admin_actions function processes a Stripe unlink action without validating a WordPress nonce, then removes stored publishable keys, secret keys, webhook secrets, and Apple Pay settings. Exploitation requires a site administrator to follow a crafted link or submit a forged request; successful deletion disables the store's Stripe payment processing.

CVSS severity4.3
Medium
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

CSRF in PeachPay Payments & Express Checkout for WooCommerce 1.120.46 and earlier allows remote attackers to delete Stripe credentials. The peachpay_stripe_handle_admin_actions function processes a Stripe unlink action without validating a WordPress nonce, then removes stored publishable keys, secret keys, webhook secrets, and Apple Pay settings. Exploitation requires a site administrator to follow a crafted link or submit a forged request; successful deletion disables the store's Stripe payment processing.

The record

CVE
CVE-2026-9618
Published
May 28, 2026
Updated
May 28, 2026
Vendor
PeachPay
Product
PeachPay Payments & Express Checkout for WooCommerce
Classifications
CWE-352, T1485
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 28, 2026CVE publishedPublication date reported by the CVE source.
  2. May 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=1.120.46

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

PeachPay · PeachPay Payments & Express Checkout for WooCommerceversion=0 <=1.120.46

Published CVSS scores

4.3WordfenceCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)
T1485Data Destruction

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo