CVE-2024-0909

Anonymous Restricted Content <= 1.6.2 - Protection Mechanism Bypass

2024-02-02 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 1.6.3
Affected Version
<= 1.6.2
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-0909
View all Anonymous Restricted Content vulnerabilities

At a glance

CVE-2024-0909 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Anonymous Restricted Content WordPress plugin, affecting versions <= 1.6.2. 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 1.6.3; sites on affected versions should update now. Disclosed February 2024, reported by Francesco Carlucci.

Vulnerability Overview

The Anonymous Restricted Content plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.6.2. This is due to insufficient restrictions through the REST API on the posts/pages that protections are being place on. This makes it possible for unauthenticated attackers to access protected content.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Anonymous Restricted Content <= 1.6.2 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Anonymous Restricted Content the fix is 1.6.3: builds <= 1.6.2 are affected, anything from 1.6.3 onward is not.

Remediation

Update to version 1.6.3, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Anonymous Restricted Content 1.6.3 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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