Severity:

HIGH RISK

(7.1)

Missing Authorization in Paid Memberships Pro for WordPress

CVE-2026-4100

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Modification of Payment Webhook Configuration and Service Disruption

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The Paid Memberships Pro plugin for WordPress contains a missing authorization vulnerability that allows low-privileged users to manage the site's Stripe webhooks via AJAX endpoints.

Authenticated attackers with only Subscriber-level access can create, delete, or rebuild Stripe webhooks, potentially disrupting payment processing, subscription renewals, cancellations, and failed payment handling.

Affected context

This issue affects WordPress sites using the Paid Memberships Pro plugin integrated with Stripe for payment processing.

The vulnerable behavior occurs in the AJAX handlers:

  • wp_ajax_pmpro_stripe_create_webhook
  • wp_ajax_pmpro_stripe_delete_webhook
  • wp_ajax_pmpro_stripe_rebuild_webhook

When these endpoints do not enforce strict capability checks, any authenticated user role at or above Subscriber can access webhook management actions that would normally be reserved for site administrators or payment managers.

Exploit preconditions

  • Attack surface: WordPress AJAX endpoints exposed by the Paid Memberships Pro plugin.
  • Required access: Authenticated WordPress account with at least Subscriber-level privileges.
  • Trigger point: Invocation of wp_ajax_pmpro_stripe_create_webhook, wp_ajax_pmpro_stripe_delete_webhook, or wp_ajax_pmpro_stripe_rebuild_webhook without proper capability checks.
  • Why exploitation is possible: The affected handlers rely on authentication alone and do not verify that the caller has sufficient authorization (e.g., administrator or equivalent capability) before performing sensitive Stripe webhook operations.

Why this happens

The root cause aligns with CWE-862: Missing Authorization. Sensitive operations for managing Stripe webhooks are exposed via AJAX handlers that check whether a user is logged in but fail to enforce appropriate capability or role checks.

In WordPress, privileged actions must be guarded by explicit capability checks (such as current_user_can(...)) or equivalent logic. When these checks are absent or overly permissive, lower-privileged users inherit access to administrative functions, enabling them to alter payment integration settings without authorization.

Potential impact

  • Attackers may delete the existing Stripe webhook, interrupting all payment event notifications.
  • Automatic subscription renewals may fail to synchronize with WordPress membership statuses.
  • Cancellation and refund events may not be reflected in the membership system, leading to revenue leakage or access control inconsistencies.
  • Failed payment events may no longer trigger downgrade or suspension workflows, causing business logic and billing desynchronization.
  • Attackers could repeatedly disrupt webhook configuration, creating ongoing denial-of-service conditions for payment processing.

General mitigation guidance

Mitigation commonly centers on enforcing strict authorization and least privilege for sensitive payment operations:

  • Guard all webhook management functions with explicit capability checks that map to administrative or payment-management roles only.
  • Treat payment gateway configuration (including webhooks) as a high-privilege area and isolate it from general site settings.
  • Apply a role and capability review to ensure that low-privileged roles (Subscriber, Customer, Member) cannot access AJAX actions or REST endpoints that modify payment integrations.
  • Use defense-in-depth controls such as nonces and intention-revealing parameters in AJAX handlers to reduce the risk of unintended or bulk changes.
  • Document and standardize an authorization pattern for all plugin administration features so new endpoints automatically follow secure defaults.

How teams detect issues like this

Effective detection approaches for similar authorization issues include:

  • Static analysis or custom linters that flag AJAX or REST handlers lacking explicit capability checks or using overly broad permissions.
  • Code review guidelines that require reviewers to locate and verify authorization logic for every endpoint touching payment or configuration state.
  • Logging of webhook management operations (create, delete, rebuild) with user identifiers and timestamps, then monitoring for unusual activity from low-privileged accounts.
  • Periodic security assessments focusing on WordPress-specific anti-patterns, such as relying solely on authentication for admin-like AJAX actions.

Sources

SourceLink
github.comgithub.com/strangerstudios/paid-memberships-pro/pull/3615
wordfence.comwordfence.com/threat-intel/vulnerabilities/id/5b333a3d-e416-42aa-9722-5406df0a64b3?source=cve

Frequently asked

questions

Yes, it can be exploited remotely, but only by users who can authenticate to the WordPress site. An attacker must have at least Subscriber-level credentials or compromise such an account.

The issue is exposed to any authenticated user with Subscriber-level access or higher. No administrative privileges are required if authorization checks are missing or inadequate.

The safest pattern is to add strict capability checks to all Stripe webhook management handlers, ensuring only roles intended to administer payment settings (typically administrators or a dedicated payment manager role) can invoke them. This should be applied consistently to all similar endpoints.

Adopt a standard access-control pattern for all privileged actions, require explicit capability checks in code reviews, and use automated checks to flag new endpoints without authorization logic. Treat payment configuration and other critical integrations as high-sensitivity areas requiring least-privilege access and thorough auditing.

Find out what's already
exploitable in your codebase.