<?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>Fri, 16 Oct 2026 23:56:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-1857 — Gutenberg Blocks with AI by Kadence WP &lt;= 3.6.1 - Authenticated (Contributor+) Server-Side Request Forgery via 'endpoin…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-1857</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 Gutenberg Blocks with AI by Kadence WP plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.6.1. This is due to insufficient validation of the `endpoint` parameter in the `get_items()` function of the GetResponse REST API handler. The endpoint&amp;#39;s permission check only requires `edit_posts` capability (Contributor role) rather than `manage_options` (Administrator). This makes it possible for authenticated attackers, with Contributor-level access and above, to make server-side requests to arbitrary endpoints on the configured GetResponse API server, retrieving sensitive data such as contacts, campaigns, and mailing lists using the site&amp;#39;s stored API credentials. The stored API key is also leaked in the request headers.&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 Gutenberg Blocks with AI by Kadence WP plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.6.1. This is due to insufficient validation of the `endpoint` parameter in the `get_items()` function of the GetResponse REST API handler. The endpoint&amp;#39;s permission check only requires `edit_posts` capability (Contributor role) rather than `manage_options` (Administrator). This makes it possible for authenticated attackers, with Contributor-level access and above, to make server-side requests to arbitrary endpoints on the configured GetResponse API server, retrieving sensitive data such as contacts, campaigns, and mailing lists using the site&amp;#39;s stored API credentials. The stored API key is also leaked in the request headers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-1857</guid>
    </item>
  </channel>
</rss>
