CVE-2026-14848

Paid Member Subscriptions <= 3.0.7 - Missing Authorization to Authenticated (Subscriber+) Cross-User Subscription Hijack

Strategic Overview

At a glance

CVE-2026-14848 is a medium-severity Missing Authorization vulnerability in the Paid Membership Subscriptions WordPress plugin, affecting versions <= 3.0.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.0.8; sites on affected versions should update now. Disclosed July 2026, reported by Revanth Hari Narayana Matte.

Vulnerability Overview

The Paid Member Subscriptions plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 3.0.7. This is due to missing ownership validation on the pms_current_subscription POST parameter in the process_checkout function, allowing any authenticated user to reference subscriptions belonging to other users. This makes it possible for authenticated attackers, with subscriber-level access and above, to hijack another user's subscription by supplying an arbitrary subscription ID during checkout, modifying or taking over subscriptions belonging to other members.

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.

CWE-862: Missing Authorization

Reaching this weakness in Paid Membership Subscriptions <= 3.0.7 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 Membership Subscriptions the fix is 3.0.8: builds <= 3.0.7 are affected, anything from 3.0.8 onward is not.

Remediation

Update to version 3.0.8, 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 Membership Subscriptions 3.0.8 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