Description
The WP Popular Posts plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.4.2 via the 'context' parameter. This makes it possible for unauthenticated attackers to extract sensitive edit-context fields — including raw title, raw content body, password, meta, status, and guid — from non-public post objects such as wp_block synced patterns that WordPress core itself refuses to expose to unauthenticated callers. This is possible because the plugin's REST route is registered with a permission_callback of __return_true and passes the caller-supplied context parameter (e.g., context=edit) directly to WP_REST_Posts_Controller::prepare_item_for_response() without invoking get_item_permissions_check() or check_read_permission(), while the underlying query accepts an arbitrary post_type value without enforcing public or show_in_rest visibility flags.
Published: 2026-10-01
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Sensitive Information Disclosure
Action: Immediate Patch
AI Analysis

Impact

The WP Popular Posts plugin allows an attacker who does not authenticate to retrieve private post data via the WordPress REST API. The plugin registers a REST route whose permission_callback always returns true and forwards the client‑supplied “context” (e.g., context=edit) directly to WP_REST_Posts_Controller::prepare_item_for_response() without running the normal read‑permission checks. Because the underlying query accepts any post_type value and does not enforce public or show_in_rest visibility flags, an unauthenticated user can read sensitive fields such as raw title, raw content, password, meta, status, and guid from posts that WordPress core normally keeps hidden, including non‑public block patterns.

Affected Systems

All installations of the WP Popular Posts WordPress plugin at version 7.4.2 or earlier are affected. The plugin is distributed under the author hcabrera and is used on WordPress sites that enable the REST API to expose post data.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity; the EPSS score is not provided, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a simple web request to the /wp-json/wp/v2/posts endpoint with the context parameter set to edit. No user credentials or elevated privileges are required. The exposed data can aid further attacks by revealing hidden post content or administrative details.

Generated by OpenCVE AI on October 1, 2026 at 05:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade WP Popular Posts to the latest version that includes the fix; versions 7.4.3 or newer eliminate the improper permission callback and data exposure.
  • If an upgrade cannot be applied immediately, block unauthenticated access to the plugin’s REST routes or replace the plugin’s permission_callback with a function that verifies read permissions before returning a response.
  • Check any custom code that calls the plugin’s REST API and remove or sanitize the context parameter for unauthenticated requests to prevent accidental data leakage.

Generated by OpenCVE AI on October 1, 2026 at 05:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 03 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 01 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
First Time appeared Hcabrera
Hcabrera wp Popular Posts
Wordpress-extensions
Wordpress-extensions wp Popular Posts
Vendors & Products Hcabrera
Hcabrera wp Popular Posts
Wordpress-extensions
Wordpress-extensions wp Popular Posts

Thu, 01 Oct 2026 04:45:00 +0000

Type Values Removed Values Added
Description The WP Popular Posts plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.4.2 via the 'context' parameter. This makes it possible for unauthenticated attackers to extract sensitive edit-context fields — including raw title, raw content body, password, meta, status, and guid — from non-public post objects such as wp_block synced patterns that WordPress core itself refuses to expose to unauthenticated callers. This is possible because the plugin's REST route is registered with a permission_callback of __return_true and passes the caller-supplied context parameter (e.g., context=edit) directly to WP_REST_Posts_Controller::prepare_item_for_response() without invoking get_item_permissions_check() or check_read_permission(), while the underlying query accepts an arbitrary post_type value without enforcing public or show_in_rest visibility flags.
Title WP Popular Posts <= 7.4.2 - Unauthenticated Information Disclosure in 'post_type' and 'context' Parameters
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

Hcabrera Wp Popular Posts
Wordpress-extensions Wp Popular Posts
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-03T15:42:52.997Z

Reserved: 2026-09-16T13:02:25.542Z

Link: CVE-2026-92548

cve-icon Vulnrichment

Updated: 2026-10-03T15:41:20.728Z

cve-icon NVD

Status : Deferred

Published: 2026-10-01T05:17:11.807

Modified: 2026-10-03T16:16:43.090

Link: CVE-2026-92548

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T15:37:48Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor