<?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 22:23:13 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-343867</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-343867</link>
      <description>EUVD-2026-343867</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-343867</guid>
    </item>
    <item>
      <title>fkie_cve-2026-6453</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-6453</link>
      <description>&lt;p&gt;The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb-&amp;gt;prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress&amp;#39;s wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb-&amp;gt;prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress&amp;#39;s wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-6453</guid>
    </item>
    <item>
      <title>GHSA-fg67-hgjg-74qh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fg67-hgjg-74qh</link>
      <description>&lt;p&gt;The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb-&amp;gt;prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress&amp;#39;s wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb-&amp;gt;prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress&amp;#39;s wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fg67-hgjg-74qh</guid>
    </item>
  </channel>
</rss>
