CVE-2026-109979 json
Related Posts for WordPress <= 3.0.0 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Exposure via 'rp4wp_create_link' Parameter
published 2026-10-28 12 d ago modified 2026-10-29 11 d ago also EUVD-2026-111747
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11 d ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- barrykooij Related Posts for WordPress
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/3ab9af6a-bfe7-4da5-8e60-b20f38cbab36?source=cve
- plugins.trac.wordpress.org /browser/related-posts-for-wp/tags/3.0.0/src/Admin/LinkScreen/Page.php#L164
- plugins.trac.wordpress.org /browser/related-posts-for-wp/tags/3.0.0/src/Links/LinkRepository.php#L86
- plugins.trac.wordpress.org /browser/related-posts-for-wp/tags/3.0.0/src/Admin/MetaBox/ManageLinks.php#L98
- plugins.trac.wordpress.org /browser/related-posts-for-wp/tags/3.0.0/src/Links/LinkRepository.php#L310
- plugins.trac.wordpress.org /changeset?reponame=&old=3757484%40related-posts-for-wp&new=3757484%40related-posts-for-wp
- plugins.trac.wordpress.org /changeset/3757484/related-posts-for-wp/trunk/src/Admin/LinkScreen/Page.php
Sources
- CVE List CVE-2026-109979
- NVD CVE-2026-109979
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.