WP Popular Posts <= 7.4.2 - Unauthenticated Information Disclosure in 'post_type' and 'context' Parameters
Strategic Overview
- Status
- Patched in 7.4.3
- Affected Plugin
- WP Popular Posts
- Affected Version
<= 7.4.2- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-92548
At a glance
CVE-2026-92548 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Popular Posts WordPress plugin, affecting versions <= 7.4.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 7.4.3; sites on affected versions should update now. Disclosed September 2026, reported by mad4cyber.
Vulnerability Overview
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.
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
WP Popular Posts <= 7.4.2 carries this weakness at context, and reaching it takes no account at all. 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 WP Popular Posts the fix is 7.4.3: builds <= 7.4.2 are affected, anything from 7.4.3 onward is not.
Remediation
Update to version 7.4.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Popular Posts 7.4.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Popular Posts
- 8.8CVE-2021-42362: WordPress Popular Posts <= 5.3.2 Arbitrary File Upload
CVE-2021-42362 - 7.3CVE-2024-11733: WordPress Popular Posts Arbitrary Shortcode Execution
CVE-2024-11733 - 6.4CVE-2023-45607: WordPress Popular Posts <= 6.3.2 Stored XSS
CVE-2023-45607 - 6.4CVE-2021-20746: WordPress Popular Posts <= 5.3.2 Cross-Site Scripting
CVE-2021-20746 - 6.1WordPress Popular Posts <= 5.5.1 Reflected Cross-Site Scripting
- 5.5CVE-2021-36872: WordPress Popular Posts <= 5.3.3 Stored XSS
CVE-2021-36872 - 5.3CVE-2022-43468: WordPress Popular Posts <= 6.0.5 Views Changes
CVE-2022-43468
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C