fixnx
mediumCVE-2026-12654

Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret

The Payment Plugins for Stripe WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to mark arbitrary pending asynchronous WooCommerce orders as paid by forging a charge.pending event with attacker-controlled metadata.order_id, metadata.gateway_id, and a charge object carrying status=succeeded and captured=true, triggering payment_complete() and downstream fulfillment flows with an attacker-supplied transaction ID. Exploitation requires the merchant to have left the webhook_secret_test or webhook_secret_live option blank, which is the plugin's default state until a Stripe-issued whsec_ value is manually configured; once a non-empty secret is set, the signature verification cannot be bypassed.

Browse WordPress security risks
ProductPayment Plugins for Stripe WooCommerce
CVSS5.3
EPSSNot scored yet
UpdatedJuly 24, 2026

Quick answer

paymentplugins Payment Plugins for Stripe WooCommerce should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <= 4.0.7
  • up to and including 4.0.7

Fixed versions

  • 4.0.8

How to fix it

CVE-2026-12654 affects Payment Plugins for Stripe WooCommerce and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Upgrade Payment Plugins for Stripe WooCommerce to 4.0.8 or a later vendor-supported fixed release.

  1. Inventory every deployment, device, package, plugin, container, build, and environment that uses Payment Plugins for Stripe WooCommerce.
  2. Compare the installed version with the recorded affected range: <= 4.0.7, *-4.0.7.
  3. Upgrade Payment Plugins for Stripe WooCommerce to 4.0.8 or a later vendor-supported fixed release.
  4. Until patched, disable the affected Payment Plugins for Stripe WooCommerce feature or plugin and restrict its public and administrator endpoints.
  5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to Payment Plugins for Stripe WooCommerce; remove access that is not required.
  6. Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
  7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-12654 in place.
  • Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
  • Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
  • Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
  • Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

WordPressWooCommerceNetwork SecurityAuthorization BypassCryptography

Related security risks

More published guidance from the same primary category.

high

CVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability

Updated July 24, 2026

critical

SAML Single Sign On <= 5.4.4 - Unauthenticated Authentication Bypass via SAMLResponse Parameter

Updated July 24, 2026

medium

Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter

Updated July 24, 2026

Trusted references

Source advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceSource advisoryNVD, WordfenceWordfence advisoryNVD, WordfenceWordfence advisoryNVD, Wordfence

FAQ

What is affected by CVE-2026-12654?

paymentplugins Payment Plugins for Stripe WooCommerce versions listed as affected should be reviewed: <= 4.0.7, up to and including 4.0.7.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.