<?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 21:27:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-5427 — Kubio AI Page Builder &lt;= 2.7.2 - Missing Authorization to Authenticated (Contributor+) Limited File Upload via Kubio Bl…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-5427</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; extendthemes Kubio AI Page Builder&lt;/p&gt;
&lt;p&gt;The Kubio plugin for WordPress is vulnerable to Arbitrary File Upload in versions up to and including 2.7.2. This is due to insufficient capability checks in the kubio_rest_pre_insert_import_assets() function, which is hooked to the rest_pre_insert_{post_type} filter for posts, pages, templates, and template parts. When a post is created or updated via the REST API, Kubio parses block attributes looking for URLs in the &amp;#39;kubio&amp;#39; attribute namespace and automatically imports them via importRemoteFile() without verifying the user has the upload_files capability. This makes it possible for authenticated attackers with Contributor-level access and above to bypass WordPress&amp;#39;s normal media upload restrictions and upload files fetched from external URLs to the media library, creating attachment posts in the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; extendthemes Kubio AI Page Builder&lt;/p&gt;
&lt;p&gt;The Kubio plugin for WordPress is vulnerable to Arbitrary File Upload in versions up to and including 2.7.2. This is due to insufficient capability checks in the kubio_rest_pre_insert_import_assets() function, which is hooked to the rest_pre_insert_{post_type} filter for posts, pages, templates, and template parts. When a post is created or updated via the REST API, Kubio parses block attributes looking for URLs in the &amp;#39;kubio&amp;#39; attribute namespace and automatically imports them via importRemoteFile() without verifying the user has the upload_files capability. This makes it possible for authenticated attackers with Contributor-level access and above to bypass WordPress&amp;#39;s normal media upload restrictions and upload files fetched from external URLs to the media library, creating attachment posts in the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-5427</guid>
    </item>
  </channel>
</rss>
