---
id: "CVE-2026-109980"
kind: "vulnerability"
aliases: ["CVE-2026-109980"]
title: "WordPress Related Posts plugin: contributors can read private post titles"
severity: "medium"
cvss: 4.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "wordpress", "wordpress-plugin"]
not_affected_if: ["no-contributor-users", "plugin-not-installed", "plugin-updated"]
published_at: "2026-10-28T07:16:45+00:00"
first_seen_at: "2026-10-28T07:31:38+00:00"
updated_at: "2026-10-28T07:33:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109980", "first_seen_at": "2026-10-28T07:31:38+00:00"}]
---

# WordPress Related Posts plugin: contributors can read private post titles

The Related Posts for WordPress plugin up to and including 3.0.0 has a flawed authorization check on the rp4wp_view parameter. An authenticated Contributor can list the titles and publication dates of all private posts on the site, which normally only Editors and above can see.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed plugin version in the WordPress admin under Plugins, or with `wp plugin get related-posts-for-wp --field=version` if WP-CLI is available.
- Confirm whether any user holds the Contributor role on the site.

## Fix

- Update the Related Posts for WordPress plugin to a version later than `3.0.0`.
- Until updated, remove untrusted Contributor accounts or deactivate the plugin.

## Timeline

- 2026-10-28T07:31:38+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109980

## From the sources

The Related Posts for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.0 via the 'rp4wp_view' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the titles and publication dates of all private posts site-wide, normally restricted to Editor-level users and above. The page's existing authorization check only verifies edit_posts and edit_post on a parent post the attacker owns, both of which any Contributor satisfies, leaving no effective gate against reading other authors' private posts.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_