---
id: CVE-2026-92548
title: >-
  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
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 …
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'
cwe:
  - CWE-200
vendor: hcabrera
product: WP Popular Posts
affected:
  - wp_popular_posts <= 7.4.2
published: '2026-10-01'
updated: '2026-10-01'
sourceUpdated: '2026-10-01T05:17:11.807'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-92548'
references:
  - url: >-
      https://plugins.trac.wordpress.org/browser/wordpress-popular-posts/tags/7.4.2/src/Query.php#L421
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/wordpress-popular-posts/tags/7.4.2/src/Rest/PostsEndpoint.php#L38
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/wordpress-popular-posts/tags/7.4.2/src/Rest/PostsEndpoint.php#L51
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/wordpress-popular-posts/tags/7.4.2/src/Rest/PostsEndpoint.php#L96
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/changeset/3715724/wordpress-popular-posts/trunk
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/changeset/3715724/wordpress-popular-posts/trunk/src/Rest/PostsEndpoint.php
    label: security@wordfence.com
  - url: >-
      https://www.wordfence.com/threat-intel/vulnerabilities/id/09c63c2f-d2d3-4c39-8329-0e0e5b62db98?source=cve
    label: security@wordfence.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-10-01T05:37:57.556Z'
---

## 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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.