CVE-2026-92548: WP Popular Posts <= 7.4.2 - Unauthenticated Information Disclosure in 'post_type' and 'context' Parameters

Published Oct 1, 2026
·
Updated

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 wpblock 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 permissioncallback of returntrue and passes the caller-supplied context parameter (e.g., context=edit) directly to WPRESTPostsController::prepareitemforresponse() without invoking getitempermissionscheck() or checkreadpermission(), while the underlying query accepts an arbitrary posttype value without enforcing public or showinrest visibility flags.

Affected Software

1 affected component
Hector Cabrera WP Popular Posts<=7.4.2

Event History

Oct 1, 2026
CVE Published
via MITRE·04:27 AM
Data Sourced
via MITRE·04:27 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any unauthenticated remote attacker can exploit it. No WordPress account, user interaction, or special privileges are required.

2

What data may be exposed?

An attacker may retrieve sensitive edit-context fields from non-public post objects, including raw titles, raw content bodies, passwords, metadata, status, and GUIDs. Synced patterns using the wp_block post type are specifically identified as affected non-public objects.

3

What conditions make a site vulnerable?

Sites using WP Popular Posts version 7.4.2 or earlier are affected. The vulnerable REST route accepts caller-controlled context and arbitrary post_type values without enforcing normal WordPress read-permission or post visibility checks.

4

Does this require a non-default configuration or a public post type?

No. The issue is specifically caused by the route allowing arbitrary post types, including non-public objects that WordPress core would normally refuse to expose to unauthenticated users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203