CVE-2026-97249

Paid Membership Subscriptions – Effortless Memberships, Recurring Payments & Content Restriction <= 3.0.9 - Unauthenticated Unauthorized Subscription Activation

2026-09-28 00:00
MYUNGYONG LEE

Strategic Overview

Status
Patched in 3.1.0
Affected Version
<= 3.0.9
CVSS
5.3Medium
Weakness type
CWE-602 · Client-Side Enforcement of Server-Side Security
CVE
CVE-2026-97249
View all Paid Membership Subscriptions – Effortless Memberships, Recurring Payments & Content Restriction vulnerabilities

At a glance

CVE-2026-97249 is a medium-severity Client-Side Enforcement of Server-Side Security vulnerability in the Paid Membership Subscriptions WordPress plugin, affecting versions <= 3.0.9. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.0; sites on affected versions should update now. Disclosed September 2026, reported by MYUNGYONG LEE.

Vulnerability Overview

The Paid Membership Subscriptions – Effortless Memberships, Recurring Payments & Content Restriction plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 3.0.9. This is due to missing server-side token validation on the Stripe SCA resume AJAX endpoint, allowing any request that supplied a valid payment intent ID to drive the handler against arbitrary member subscriptions. This makes it possible for unauthenticated attackers to complete another member's Stripe SCA authentication flow using only a known payment intent ID, activating or altering a subscription without authorization.

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 privileges on the target site, and no interaction from a victim user.

CWE-602: Client-Side Enforcement of Server-Side Security

The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.

Remediation

Update to version 3.1.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Paid Membership Subscriptions 3.1.0 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