<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 14:29:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-3454 — GenerateBlocks &lt;= 2.2.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Exposu…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-3454</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; edge22 GenerateBlocks&lt;/p&gt;
&lt;p&gt;The GenerateBlocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2.0. This is due to missing object-level authorization checks in the /wp-json/generateblocks/v1/dynamic-tag-replacements REST endpoint. The endpoint only verifies that the user has the edit_posts capability but does not verify the user has permission to access the specific post or its associated data referenced by attacker-controlled id parameters in dynamic tag content. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive information from arbitrary posts including author email addresses and non-protected post meta values by crafting dynamic tag payloads such as {{post_meta id:&amp;lt;target&amp;gt;|key:&amp;lt;meta_key&amp;gt;}} and {{post_title id:&amp;lt;target&amp;gt;|link:author_email}}.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; edge22 GenerateBlocks&lt;/p&gt;
&lt;p&gt;The GenerateBlocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2.0. This is due to missing object-level authorization checks in the /wp-json/generateblocks/v1/dynamic-tag-replacements REST endpoint. The endpoint only verifies that the user has the edit_posts capability but does not verify the user has permission to access the specific post or its associated data referenced by attacker-controlled id parameters in dynamic tag content. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive information from arbitrary posts including author email addresses and non-protected post meta values by crafting dynamic tag payloads such as {{post_meta id:&amp;lt;target&amp;gt;|key:&amp;lt;meta_key&amp;gt;}} and {{post_title id:&amp;lt;target&amp;gt;|link:author_email}}.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-3454</guid>
    </item>
  </channel>
</rss>
