Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Contributor
-
ExploitAccess Related Posts link screen
-
ExecutionManipulate rp4wp_view parameter
-
ImpactEnumerate private post titles and dates
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with Contributor-level capabilities (or higher) on a site running Related Posts for WordPress 3.0.0 or earlier; the attacker must own at least one parent post so the plugin's edit_posts/edit_post check on that post passes, then reach the admin Related Posts link screen and supply the 'rp4wp_view' parameter. Limiting factors: exploitation is gated by valid low-privilege authentication (PR:L - most relevant on multi-author sites where untrusted Contributors exist), and the disclosure is limited to private-post titles and publication dates, not post bodies, private data content, or credentials. On single-author or tightly controlled sites with no low-trust Contributor accounts, realistic exposure is minimal. |
| Impact | This is a low-to-moderate severity authorization flaw (CWE-862, Missing Authorization) whose real-world priority is modest. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) tells a consistent story: network-reachable and low-complexity, but requiring an authenticated Contributor-level account (PR:L), with only a limited confidentiality impact (C:L) and no integrity or availability impact. The impact is narrow - exposure of titles and publication dates of other authors' private posts, not full post content, credentials, or site compromise. No EPSS score, KEV listing, or SSVC automatable/technical-impact data is provided in the input, so exploitation probability cannot be quantified from the signals given; the only priority signal is the vuln.today 'this_month' label, which aligns with a non-emergency but patch-worthy issue. There is no public exploit identified in the input - the references are a Wordfence advisory and plugin source/changeset links, not working exploit code. The CVSS vector and the description agree (both point to a logged-in low-privilege attacker), so there is no network-vs-local or auth conflict to reconcile. Net assessment: a genuine broken-access-control bug worth patching on a normal cycle, not a high-urgency emergency, given the authentication requirement and the limited metadata-only disclosure. |
| Exploit ScenarioDerived | A user with only Contributor-level access to a multi-author WordPress site logs in and visits the plugin's Related Posts link screen, supplying the 'rp4wp_view' parameter against a parent post they own. Because the page only checks edit_posts and edit_post on that attacker-owned parent - capabilities any Contributor holds - the attacker is able to enumerate the titles and publication dates of every private post site-wide, information normally restricted to Editors and above. No public exploit code is identified in the input, and exploitation requires a valid low-privilege account on the target site. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Missing authorization in the Related Posts for WordPress plugin (barrykooij) through version 3.0.0 lets any authenticated Contributor-level user enumerate the titles and publication dates of every private post site-wide by supplying the 'rp4wp_view' parameter to the plugin's admin link screen. The only gate on that screen verifies edit_posts and edit_post against a parent post the attacker already owns - capabilities every Contributor holds - so nothing prevents the private-post query from returning other authors' data. Disclosure is confined to titles and publication dates rather than post bodies or credentials, exploitation requires a valid low-privilege account, and no public exploit code has been identified at time of analysis; the current priority is this_month rather than emergency action.
RemediationAI
Upgrade Related Posts for WordPress past 3.0.0: the vendor has published a fix in the plugin's Trac changeset 3757484 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3757484%40related-posts-for-wp&new=3757484%40related-posts-for-wp), so the corrected code is available upstream, but a specific released patched version number is not stated in the available data - verify the current release on the WordPress.org plugin page and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/6c197521-6e8d-4cdc-b4a3-0c165ea5ff6a) before rollout. If an upgrade cannot be completed immediately, deactivate the plugin (it removes related-post functionality and any existing related-post output on the front end), or, where the plugin must stay live, remove Contributor accounts and restrict post-authoring to roles you trust, since the flaw is only reachable by an authenticated user holding edit_posts plus ownership of some post; note that this reduces collaboration workflows on multi-author sites and does not protect sites that legitimately grant Contributor access. Reviewing private-post titles and publication dates for signs of enumeration after any suspected Contributor compromise is worthwhile given the disclosure is limited to that metadata.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WordPress gates access to private post content through capabilities such as read_private_posts and edit_others_posts, which are granted to Editor-level roles and above, not to Contributors. This plugin (CPE cpe:2.3:a:barrykooij:related_posts_for_wordpress) implements an admin link-management screen split across src/Admin/LinkScreen/Page.php and src/Admin/LinkScreen/ListTable.php, and the code at those locations performs its authorization check with edit_posts and edit_post against a parent post supplied by the caller. Because both capabilities are baseline for Contributors, the check authenticates ownership of an unrelated post rather than authorization to read private posts, which is CWE-862 (Missing Authorization): the private-post listing path reached through the 'rp4wp_view' parameter is never constrained by a capability that would actually restrict it. The result is a scoped information exposure - post titles and publication dates only - that inherits the CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, so it is a confidentiality-only, low-impact disclosure that is nonetheless fully network-reachable once a low-privileged account exists. There is no CISA KEV listing and no public exploit code identified at time of analysis.
Know when Related Posts For Wordpress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Contributor authentication is required (PR:L), it is remotely reachable with a simple request (AV:N/AC:L/UI:N), and only limited metadata of private posts leaks (C:L, I:N, A:N).
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-111754
GHSA-jcpv-fxpw-qc4w
NVD
CVE.org
EPSS
Exploit-DB