Security Resilience

CVE-2025-14844

Access Control in Liquidweb Restrict Content ≤ 3.2.17

Published
16 January 2026
Modified
23 January 2026
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.0046 38th percentile
Risk Priority 61 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-14844 is a high-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Liquidweb Restrict Content. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-14844 is a missing authentication vulnerability (CWE-639) in the Membership Plugin – Restrict Content for WordPress, affecting all versions up to and including 3.2.16. The issue resides in the 'rcp_stripe_create_setup_intent_for_saved_card' function within the plugin's Stripe gateway integration at core/includes/gateways/stripe/functions.php. Due to a missing capability check and failure to validate a user-controlled key, the function exposes sensitive Stripe SetupIntent client_secret values.

Unauthenticated attackers can exploit this vulnerability over the network with low attack complexity and no user interaction required, per its CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N). Exploitation allows remote attackers to leak Stripe SetupIntent client_secret values for any membership, granting high confidentiality impact and limited integrity impact by compromising payment setup intents without affecting availability.

Mitigation is available in version 3.2.17 of the plugin, as detailed in WordPress plugin repository changeset 3438168, which addresses the flaws in core/includes/gateways/stripe/functions.php. Practitioners should urge site administrators to update immediately, verify Stripe configurations, and monitor for unauthorized SetupIntent access using Stripe's API documentation.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Missing Authentication in all versions up to, and including, 3.2.16 via the 'rcp_stripe_create_setup_intent_for_saved_card' function due to missing capability check. Additionally, the plugin does not check a user-controlled key,…

more

which makes it possible for unauthenticated attackers to leak Stripe SetupIntent client_secret values for any membership.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-3182Same product: Liquidweb Restrict Content
CVE-2023-47668Same product: Liquidweb Restrict Content
CVE-2024-11090Same product: Liquidweb Restrict Content
CVE-2024-13457Same vendor: Liquidweb
CVE-2025-43732Shared CWE-639
CVE-2026-80197Shared CWE-639
CVE-2026-3307Shared CWE-639
CVE-2023-44254Shared CWE-639
CVE-2024-12767Shared CWE-639
CVE-2025-30257Shared CWE-639

Affected Assets

liquidweb
restrict content
≤ 3.2.17

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Enforcing approved authorizations on every access request structurally stops a user-controlled key from reaching another user's data.

Requiring explicit access-control decisions on each request blocks unauthorized key-driven access.

Least-privilege restrictions limit the scope of data reachable even if a key check is bypassed.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
blocks

Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.

PR.IR-01 mostly match
blocks

Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes

A.8.3 mandates that access to information be restricted based on user identity and permissions, directly addressing the missing authorization check that defines CWE-639; when applied, it removes the vulnerability by requiring that such checks be implemented.

blocks

A.5.15 directly requires defining and implementing access control rules (including authorization, need-to-know, role-based restrictions, formal requests, and consistency with classification) that stop one user from reaching another's data via a tampered key; the bounded remainder is dynamic or application-specific authorization logic (cross-referenced to 8.26) that may still allow bypass if those downstream rules are flawed.

finds

Security testing can detect missing authorization checks but does not prevent the weakness in production.

blocks

Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.

prevents

Secure coding practices reduce the likelihood of missing authorization checks but do not guarantee their presence at runtime.

References