CVE-2026-4100 HIGH

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

Vendor Strangerstudios
Product Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions
Weakness CWE-862 · Missing authorization
Published May 2, 2026
Last update May 4, 2026

CVSS base score

7.1/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Paid Memberships Pro versions up to 3.6.5 lack proper authorization checks, allowing authenticated users with low privileges to modify site content and disrupt service availability. An attacker with a basic user account can alter pages or posts and cause the site to become unavailable. Site administrators should update immediately to a version newer than 3.6.5.

What an attacker can do

03Attacker Capabilities

Modify site content and make the site unavailable.

Potential impact on your site

04Site Impact

Unauthorized users can deface content and cause downtime; site availability and integrity are at risk.

Conditions required to exploit

05Prerequisites

Attacker needs a low-privilege user account on the site.

Key dates

06Disclosure timeline

May 2, 2026 CVE published
May 4, 2026 Record updated

Related vulnerabilities

08Related CVE