<?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, 02 Oct 2026 10:02:16 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-354483</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354483</link>
      <description>EUVD-2026-354483</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354483</guid>
    </item>
    <item>
      <title>fkie_cve-2026-15993</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-15993</link>
      <description>&lt;p&gt;The Form Maker by 10Web – Mobile-Friendly Drag &amp;amp; Drop Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via &amp;#39;{username}&amp;#39; Placeholder in Dynamic-Choice Field WHERE Clause in all versions up to, and including, 1.15.44 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This requires that a form is configured with a DB-backed dynamic choice field whose WHERE template references the {username} placeholder, and the attacker must first set their own display_name to a SQL payload via the standard WordPress profile edit screen before triggering the fm_reload_input AJAX endpoint.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Form Maker by 10Web – Mobile-Friendly Drag &amp;amp; Drop Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via &amp;#39;{username}&amp;#39; Placeholder in Dynamic-Choice Field WHERE Clause in all versions up to, and including, 1.15.44 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This requires that a form is configured with a DB-backed dynamic choice field whose WHERE template references the {username} placeholder, and the attacker must first set their own display_name to a SQL payload via the standard WordPress profile edit screen before triggering the fm_reload_input AJAX endpoint.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-15993</guid>
    </item>
    <item>
      <title>GHSA-6pwj-j8g4-g6fg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6pwj-j8g4-g6fg</link>
      <description>&lt;p&gt;The Form Maker by 10Web – Mobile-Friendly Drag &amp;amp; Drop Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via &amp;#39;{username}&amp;#39; Placeholder in Dynamic-Choice Field WHERE Clause in all versions up to, and including, 1.15.44 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This requires that a form is configured with a DB-backed dynamic choice field whose WHERE template references the {username} placeholder, and the attacker must first set their own display_name to a SQL payload via the standard WordPress profile edit screen before triggering the fm_reload_input AJAX endpoint.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Form Maker by 10Web – Mobile-Friendly Drag &amp;amp; Drop Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via &amp;#39;{username}&amp;#39; Placeholder in Dynamic-Choice Field WHERE Clause in all versions up to, and including, 1.15.44 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This requires that a form is configured with a DB-backed dynamic choice field whose WHERE template references the {username} placeholder, and the attacker must first set their own display_name to a SQL payload via the standard WordPress profile edit screen before triggering the fm_reload_input AJAX endpoint.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6pwj-j8g4-g6fg</guid>
    </item>
  </channel>
</rss>
