Skip to main content

CVE-2024-0680: WP Private Content Plus Information Disclosure

CVE-2024-0680 is an information disclosure vulnerability in WP Private Content Plus that exposes private posts through the REST API. Unauthenticated attackers can view protected content. This article covers technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-0680 Overview

CVE-2024-0680 affects the WP Private Content Plus plugin for WordPress in all versions up to and including 3.6. The plugin fails to restrict access to posts through the WordPress REST API when those posts are marked as private. Unauthenticated attackers can retrieve the content of protected posts by querying REST API endpoints directly, bypassing the access controls the plugin is designed to enforce. The flaw is classified under [CWE-693] Protection Mechanism Failure and results in information disclosure of content the site owner intended to restrict.

Critical Impact

Unauthenticated remote attackers can read posts and pages that site administrators have designated as private, exposing confidential content through standard REST API requests.

Affected Products

  • WP Private Content Plus plugin for WordPress, versions ≤ 3.6
  • Developed by wpexpertdeveloper
  • Distributed via the WordPress plugin repository

Discovery Timeline

  • 2024-02-28 - CVE-2024-0680 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-0680

Vulnerability Analysis

WP Private Content Plus adds visibility controls to WordPress posts and pages. Administrators can mark content as private so that only authenticated users or specific roles can view it. The plugin enforces these restrictions in the standard WordPress rendering path but does not apply equivalent checks when content is requested through the REST API.

As a result, an attacker can bypass the plugin's access controls simply by requesting the same post through the /wp-json/wp/v2/posts/ endpoint or similar REST routes. The REST API returns the full post content without evaluating the plugin's privacy metadata, exposing data the administrator intended to restrict.

The weakness falls under [CWE-693] because a protection mechanism exists but is incompletely enforced across all content delivery paths.

Root Cause

The root cause is inconsistent enforcement of the plugin's access control logic. WP Private Content Plus hooks into the traditional WordPress post rendering filters but omits the equivalent rest_prepare_post or rest_request_before_callbacks filters that would allow it to inspect and block REST responses for restricted content.

Attack Vector

Exploitation requires only network access to the target WordPress site. No authentication, user interaction, or elevated privileges are needed. An attacker enumerates post IDs through the public REST API and requests any post flagged as private by the plugin. Because the REST endpoint ignores the plugin's visibility rules, the response includes the full title, content, and metadata of the private post.

No verified public proof-of-concept code is available. Readers can review the plugin fix in the WordPress Changeset Update and the Wordfence Vulnerability Report for technical specifics.

Detection Methods for CVE-2024-0680

Indicators of Compromise

  • Unauthenticated HTTP GET requests to /wp-json/wp/v2/posts/ or /wp-json/wp/v2/pages/ endpoints targeting post IDs that correspond to privacy-restricted content.
  • Access logs showing enumeration patterns across sequential post IDs from a single source address.
  • REST API responses returning HTTP 200 for posts that render as restricted when fetched through the standard web interface.

Detection Strategies

  • Compare REST API response bodies against the rendered HTML output for the same post ID; divergence on posts protected by WP Private Content Plus indicates exploitation.
  • Alert on high volumes of /wp-json/wp/v2/ requests originating from unauthenticated sessions.
  • Inventory WordPress installations to identify sites running WP Private Content Plus versions ≤ 3.6.

Monitoring Recommendations

  • Enable verbose web server logging for all /wp-json/ paths and retain logs for correlation.
  • Monitor WordPress plugin update feeds and the Wordfence threat intelligence stream for new advisories affecting WP Private Content Plus.
  • Track outbound REST API usage patterns to detect scraping behavior consistent with content enumeration.

How to Mitigate CVE-2024-0680

Immediate Actions Required

  • Update WP Private Content Plus to a version later than 3.6 as soon as the patched release is available from the plugin repository.
  • Audit WordPress sites for the presence of the vulnerable plugin and inventory any content marked as private.
  • Review web server logs for unauthenticated REST API requests targeting restricted posts since February 2024.

Patch Information

The plugin maintainer committed a fix referenced in the WordPress Changeset Update. Site administrators should install the latest release available from the WordPress Plugin Overview page. Confirm the installed version through the WordPress admin dashboard after updating.

Workarounds

  • Disable the WordPress REST API for unauthenticated users through a security plugin or custom rest_authentication_errors filter until the patch is applied.
  • Restrict access to /wp-json/ endpoints at the web server or Web Application Firewall layer, allowing only authenticated sessions.
  • Deactivate WP Private Content Plus and migrate restricted content to a native WordPress access control mechanism if immediate patching is not possible.
bash
# Example nginx rule to block unauthenticated REST API access to posts
location ~ ^/wp-json/wp/v2/(posts|pages) {
    if ($http_cookie !~* "wordpress_logged_in") {
        return 403;
    }
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.