<?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>Thu, 08 Oct 2026 15:42:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-12904 — Kadence Blocks &lt;= 3.7.7 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Optimizer Data Del…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-12904</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; stellarwp Kadence Blocks — Page Builder Toolkit for Gutenberg Editor&lt;/p&gt;
&lt;p&gt;The Kadence Blocks – Gutenberg Blocks for Page Builder Features plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to and including 3.7.7. This is due to a mismatch between the object used for authorization and the object actually accessed in the Optimize_Rest_Controller&amp;#39;s create_item(), get_item(), delete_item(), and bulk_delete_items() endpoints — authorization is checked via current_user_can(&amp;#39;edit_post&amp;#39;/&amp;#39;delete_post&amp;#39;, $post_id) against the user-supplied post_id, while the storage layer keys analysis records on sha256($post_path) from a separately supplied, attacker-controlled post_path parameter, with no enforcement that post_path corresponds to post_id. This makes it possible for authenticated attackers, with Contributor-level access and above, to read or delete optimizer analysis records belonging to posts owned by other users by submitting their own post_id (which passes the capability check) together with the victim post&amp;#39;s path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; stellarwp Kadence Blocks — Page Builder Toolkit for Gutenberg Editor&lt;/p&gt;
&lt;p&gt;The Kadence Blocks – Gutenberg Blocks for Page Builder Features plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to and including 3.7.7. This is due to a mismatch between the object used for authorization and the object actually accessed in the Optimize_Rest_Controller&amp;#39;s create_item(), get_item(), delete_item(), and bulk_delete_items() endpoints — authorization is checked via current_user_can(&amp;#39;edit_post&amp;#39;/&amp;#39;delete_post&amp;#39;, $post_id) against the user-supplied post_id, while the storage layer keys analysis records on sha256($post_path) from a separately supplied, attacker-controlled post_path parameter, with no enforcement that post_path corresponds to post_id. This makes it possible for authenticated attackers, with Contributor-level access and above, to read or delete optimizer analysis records belonging to posts owned by other users by submitting their own post_id (which passes the capability check) together with the victim post&amp;#39;s path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-12904</guid>
    </item>
  </channel>
</rss>
