CVE-2026-110285

WP Stripe Checkout < 1.2.2.62 - Unauthenticated Forged Payment Completion via an Unset Webhook Signing Secret

Published Oct 25, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The WP Stripe Checkout WordPress plugin before 1.2.2.62 does not verify the Stripe webhook signature when no signing secret is configured, which is its default state, allowing unauthenticated attackers to forge a payment completion notification and create a completed order without paying.

Analysis

AI-generated

Technical impact

The WP Stripe Checkout plugin for WordPress fails to verify the Stripe webhook signature when no signing secret is configured, which is the default state. As a result, unauthenticated attackers can forge a payment completion notification, causing the system to create a completed order without any actual payment. This does not compromise user credentials or confidentiality but directly impacts the integrity of transaction records and can result in significant financial loss for the site owner.

Affected Systems

This vulnerability affects the WP Stripe Checkout WordPress plugin for all versions prior to 1.2.2.62. The affected product is the plugin itself, with the specific vulnerable release line being any installation older than 1.2.2.62.

Risk and Exploitability

Based on the description, it is inferred that the attacker can send a crafted HTTP request that mimics a Stripe webhook to the plugin endpoint because the plugin does not validate the signature when no signing secret is configured. This lack of authentication allows the order to be marked as paid. The EPSS score is less than 1%, indicating a very low exploitation probability, but the absence of signature verification makes the vulnerability moderately exploitable. The CVSS score of 5.3 reflects moderate severity. It is not yet listed in CISA's KEV catalog, yet the risk of financial exploitation remains due to the low effort required to craft the request.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update WP Stripe Checkout to version 1.2.2.62 or later
  • Configure a valid Stripe webhook signing secret in the plugin settings
  • Disable unused webhooks or restrict the callback URL to trusted domains

Generated by OpenCVE AI on October 26, 2026 at 14:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-291
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-287
CWE-291
Type Values Removed Values Added
Description The WP Stripe Checkout WordPress plugin before 1.2.2.62 does not verify the Stripe webhook signature when no signing secret is configured, which is its default state, allowing unauthenticated attackers to forge a payment completion notification and create a completed order without paying.
Title WP Stripe Checkout < 1.2.2.62 - Unauthenticated Forged Payment Completion via an Unset Webhook Signing Secret
References

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 26, 2026, 10:13 AM
Reserved
Oct 13, 2026, 7:33 PM
Status
Deferred
Published
Oct 25, 2026, 6:16 AM
Modified
Oct 26, 2026, 1:50 PM