Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-9832 medium CVSS 5.3

Vulnerability in Payment Gateway of Stripe for WooCommerce (WordPress plugin) (CVE-2026-9832)

Summary

Vulnerability in Payment Gateway of Stripe for WooCommerce (WordPress plugin) (CVE-2026-9832). Risk of unauthorized operations or information disclosure. Exploitable via woocommerce_api_wt_stripe.

Original description

The description as published by the source.

The Payment Gateway of Stripe for WooCommerce plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in all versions up to, and including, 5.0.8. This is due to the publicly accessible woocommerce_api_wt_stripe webhook endpoint (EH_Stripe_Webhook_Handler::handle()) wrapping the only call to \Stripe\Webhook::constructEvent() inside an if (!empty($endpoint_secret)) guard that is never entered on default installations — because the eh_stripe_webhook_secret option is empty after a fresh plugin install — causing the raw, attacker-controlled POST body to be decoded and processed as a fully trusted Stripe event without any signature verification, authentication, or authorization. This makes it possible for unauthenticated attackers to send forged Stripe webhook events to manipulate WooCommerce order statuses, including marking unpaid orders as paid or completed via payment_complete(), forcing legitimate orders into a failed state, fabricating dispute notifications, and injecting forged refund events. This vulnerability is only exploitable when the Stripe webhook signing secret has not been configured by an administrator; once a valid signing secret is saved, \Stripe\Webhook::constructEvent() is enforced and forged requests are rejected.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-9832 has been found in Payment Gateway of Stripe for WooCommerce (WordPress plugin).
Attackers can target a specific entry point like woocommerce_api_wt_stripe over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Payment Gateway of Stripe for WooCommerce (WordPress plugin) CVE-2026-9832" on the vendor's site.

CVE-2026-9832 (Payment Gateway of Stripe for WooCommerce (WordPress plugin)) — CWE-347 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: woocommerce_api_wt_stripe / eh_stripe_webhook_secret
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-347) exists in Payment Gateway of Stripe for WooCommerce (WordPress plugin). Attackers reach the vulnerable code path via woocommerce_api_wt_stripe without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Payment Gateway of Stripe for WooCommerce (WordPress plugin). Attack surface: woocommerce_api_wt_stripe / eh_stripe_webhook_secret.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Payment Gateway of Stripe for WooCommerce (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details