Restrict Content <= 3.2.2 - Missing Authorization to Notice Dismissal

2023-06-23 00:00
Anonymous

Strategic Overview

Status
Patched in 3.2.3
Affected Plugin
Membership Plugin – Kadence Memberships
Affected Version
< 3.2.3
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Membership Plugin – Kadence Memberships vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Membership Plugin WordPress plugin, affecting versions < 3.2.3. 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.2.3; sites on affected versions should update now. Disclosed June 2023.

Vulnerability Overview

The Restrict Content plugin for WordPress is vulnerable to unauthorized notice dismissal due to a missing capability check on the rcp_ajax_dismissed_notice_handler() function in versions up to, and including, 3.2.2. This makes it possible for authenticated attackers with subscriber-level access and above to dismiss plugin notices.

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-862: Missing Authorization

Membership Plugin < 3.2.3 carries this weakness at rcp_ajax_dismissed_notice_handler(), and reaching it takes a caller who can reach the endpoint. 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 Membership Plugin the fix is 3.2.3: builds < 3.2.3 are affected, anything from 3.2.3 onward is not.

Remediation

Update to version 3.2.3, 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: Membership Plugin 3.2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/79bb311d-d10d-4e4e-b690-84c0051b9911

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C