CVE-2026-4100

Paid Memberships Pro <= 3.6.5 - Missing Authorization to Authenticated (Subscriber+) Stripe Webhook Deletion and Payment Processing Disruption

2026-05-01 00:00
Jared Reyes

Strategic Overview

At a glance

CVE-2026-4100 is a high-severity Missing Authorization vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions <= 3.6.5. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.6.6; sites on affected versions should update now. Disclosed May 2026, reported by Jared Reyes.

Vulnerability Overview

The Paid Memberships Pro plugin for WordPress is vulnerable to unauthorized modification and disruption of Stripe webhook configuration in all versions up to, and including, 3.6.5. This is due to missing capability checks on the `wp_ajax_pmpro_stripe_create_webhook`, `wp_ajax_pmpro_stripe_delete_webhook`, and `wp_ajax_pmpro_stripe_rebuild_webhook` AJAX handlers. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete, create, or rebuild the site's Stripe webhook, disrupting all payment processing, subscription renewal synchronization, cancellation handling, and failed payment management.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on availability.

CWE-862: Missing Authorization

Reaching this weakness in Paid Memberships Pro <= 3.6.5 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Paid Memberships Pro the fix is 3.6.6: builds <= 3.6.5 are affected, anything from 3.6.6 onward is not.

Remediation

Update to version 3.6.6, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Paid Memberships Pro 3.6.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C