CVE-2026-92548 hcabrera CVE debrief

Who should care

Defenders responsible for WordPress installations using the WP Popular Posts plugin should assess exposure and prioritize verification and remediation efforts, especially for non-public post objects that may contain sensitive information. This includes reviewing the plugin version, assessing the impact on their systems, and implementing additional security measures to protect sensitive edit-context fields.

Why it matters

The WP Popular Posts plugin for WordPress is vulnerable to Sensitive Information Exposure, allowing unauthenticated attackers to extract sensitive information from non-public post objects. Defenders should prioritize verifying exposure and assessing the impact on their systems.

• Unauthenticated attackers can extract sensitive edit-context fields from non-public post objects
• Defenders need to verify exposure and assess the impact on their systems
• Remediation priority is high for systems using the WP Popular Posts plugin

Technical summary

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. The vulnerability is caused by the plugin's REST route being registered with a permission_callback of __return_true and passing the caller-supplied context parameter directly to WP_REST_Posts_Controller::prepare_item_for_response() without invoking get_item_permissions_check() or check_read_permission().

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those using the WP Popular Posts plugin.

Recommended defensive actions

• Verify the WP Popular Posts plugin version and update to a patched version if necessary
• Assess the impact of this vulnerability on non-public post objects
• Implement additional security measures to protect sensitive edit-context fields
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the plugin's REST route being registered with a permission_callback of __return_true and passing the caller-supplied context parameter directly to WP_REST_Posts_Controller::prepare_item_for_response() without invoking get_item_permissions_check() or check_read_permission().

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.