---
id: CVE-2026-9832
title: >-
  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
summary: >-
  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_…
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'
cwe:
  - CWE-347
vendor: themehigh
product: Payment Gateway of Stripe for WooCommerce
affected:
  - payment_gateway_of_stripe_for_woocommerce <= 5.0.8
published: '2026-09-19'
updated: '2026-09-21'
sourceUpdated: '2026-09-21T13:33:33.387'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-9832'
references:
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L18
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L321
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L66
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.7/includes/class-eh-stripe-webhook-handler.php#L93
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L18
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L321
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L66
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/payment-gateway-stripe-and-woocommerce-integration/tags/5.0.8/includes/class-eh-stripe-webhook-handler.php#L93
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/changeset?reponame=&old=3575195%40payment-gateway-stripe-and-woocommerce-integration&new=3575195%40payment-gateway-stripe-and-woocommerce-integration
    label: security@wordfence.com
  - url: >-
      https://www.wordfence.com/threat-intel/vulnerabilities/id/2cef154c-efb8-4455-9be6-e3cf8b95e9d3?source=cve
    label: security@wordfence.com
tags:
  - nvd
  - cve.org
epss: 0.00226
epssPercentile: 0.13588
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-09-19T13:24:24.417063Z'
ingestedAt: '2026-09-19T07:59:56.112Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.