# CVE-2026-4100: Missing authorization in Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions

> Authenticated subscribers can delete or modify Stripe webhooks, disrupting payment processing and subscription management in Paid Memberships Pro.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-995f-rphp-2rcg

## What is CVE-2026-4100?

CVE-2026-4100 is a high-severity missing authorization vulnerability in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-4100?


## How do I fix CVE-2026-4100?

No fix has been published for CVE-2026-4100 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4100 being exploited?

There is no known exploitation of CVE-2026-4100 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4100 and fix it if it is affected.

What it is: CVE-2026-4100 is a high-severity missing authorization vulnerability in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4100 in the wild and no public exploit code.

Affected product: strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4100/ (Markdown: https://insights.sbomify.com/CVE-2026-4100/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4100
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4100
- OSV: https://osv.dev/vulnerability/CVE-2026-4100

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4100/
Summaries are generated and may contain mistakes; the official description above is the record.