<?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 05:13:33 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-287419</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-287419</link>
      <description>EUVD-2026-287419</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-287419</guid>
    </item>
    <item>
      <title>fkie_cve-2026-2412</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-2412</link>
      <description>&lt;p&gt;The Quiz and Survey Master (QSM) plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;merged_question&amp;#39; parameter in all versions up to, and including, 10.3.5. This is due to insufficient sanitization of user-supplied input before being used in a SQL query. The sanitize_text_field() function applied to the merged_question parameter does not prevent SQL metacharacters like ), OR, AND, and # from being included in the value, which is then directly concatenated into a SQL IN() clause without using $wpdb-&amp;gt;prepare() or casting values to integers. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Quiz and Survey Master (QSM) plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;merged_question&amp;#39; parameter in all versions up to, and including, 10.3.5. This is due to insufficient sanitization of user-supplied input before being used in a SQL query. The sanitize_text_field() function applied to the merged_question parameter does not prevent SQL metacharacters like ), OR, AND, and # from being included in the value, which is then directly concatenated into a SQL IN() clause without using $wpdb-&amp;gt;prepare() or casting values to integers. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-2412</guid>
    </item>
    <item>
      <title>GHSA-p9xr-7rv6-w58f</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p9xr-7rv6-w58f</link>
      <description>&lt;p&gt;The Quiz and Survey Master (QSM) plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;merged_question&amp;#39; parameter in all versions up to, and including, 10.3.5. This is due to insufficient sanitization of user-supplied input before being used in a SQL query. The sanitize_text_field() function applied to the merged_question parameter does not prevent SQL metacharacters like ), OR, AND, and # from being included in the value, which is then directly concatenated into a SQL IN() clause without using $wpdb-&amp;gt;prepare() or casting values to integers. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Quiz and Survey Master (QSM) plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;merged_question&amp;#39; parameter in all versions up to, and including, 10.3.5. This is due to insufficient sanitization of user-supplied input before being used in a SQL query. The sanitize_text_field() function applied to the merged_question parameter does not prevent SQL metacharacters like ), OR, AND, and # from being included in the value, which is then directly concatenated into a SQL IN() clause without using $wpdb-&amp;gt;prepare() or casting values to integers. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p9xr-7rv6-w58f</guid>
    </item>
  </channel>
</rss>
