<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 29 Oct 2026 13:19:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-109979 — Related Posts for WordPress &lt;= 3.0.0 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Expo…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-109979</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; barrykooij Related Posts for WordPress&lt;/p&gt;
&lt;p&gt;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 &amp;#39;rp4wp_create_link&amp;#39; parameter of the hidden &amp;#39;rp4wp_link_related&amp;#39; 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(&amp;#39;get_post&amp;#39;, $child_ids) — bypassing read_private_posts/read_post capability checks — and then echoes esc_html($child-&amp;gt;post_title) in the parent&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; barrykooij Related Posts for WordPress&lt;/p&gt;
&lt;p&gt;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 &amp;#39;rp4wp_create_link&amp;#39; parameter of the hidden &amp;#39;rp4wp_link_related&amp;#39; 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(&amp;#39;get_post&amp;#39;, $child_ids) — bypassing read_private_posts/read_post capability checks — and then echoes esc_html($child-&amp;gt;post_title) in the parent&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-109979</guid>
    </item>
  </channel>
</rss>
