<?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://vulnerability.circl.lu</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, 29 Sep 2026 03:42:30 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-15462</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-15462</link>
      <description>&lt;p&gt;The Sticky Chat Widget plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;scw_form_fields&amp;#39; parameter array keys of the &amp;#39;scw_save_form_data&amp;#39; AJAX action in versions up to, and including, 1.4.2. This is due to the save_form_data() function passing attacker-controlled POST array keys unsanitized to $wpdb-&amp;gt;insert(), which wraps column identifiers in backticks without escaping them, allowing a backtick in an attacker-supplied key to break out of the column-identifier list into raw SQL; additionally, the use of filter_input() bypasses WordPress&amp;#39;s wp_magic_quotes() protection, and the widget_id validation loop is skipped entirely when no valid widget_id is supplied, leaving $isValid at 1. This makes it possible for unauthenticated attackers 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 Sticky Chat Widget plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;scw_form_fields&amp;#39; parameter array keys of the &amp;#39;scw_save_form_data&amp;#39; AJAX action in versions up to, and including, 1.4.2. This is due to the save_form_data() function passing attacker-controlled POST array keys unsanitized to $wpdb-&amp;gt;insert(), which wraps column identifiers in backticks without escaping them, allowing a backtick in an attacker-supplied key to break out of the column-identifier list into raw SQL; additionally, the use of filter_input() bypasses WordPress&amp;#39;s wp_magic_quotes() protection, and the widget_id validation loop is skipped entirely when no valid widget_id is supplied, leaving $isValid at 1. This makes it possible for unauthenticated attackers 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://vulnerability.circl.lu/vuln/fkie_cve-2026-15462</guid>
    </item>
    <item>
      <title>GHSA-x4cw-pxp4-3x6g</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-x4cw-pxp4-3x6g</link>
      <description>&lt;p&gt;The Sticky Chat Widget plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;scw_form_fields&amp;#39; parameter array keys of the &amp;#39;scw_save_form_data&amp;#39; AJAX action in versions up to, and including, 1.4.2. This is due to the save_form_data() function passing attacker-controlled POST array keys unsanitized to $wpdb-&amp;gt;insert(), which wraps column identifiers in backticks without escaping them, allowing a backtick in an attacker-supplied key to break out of the column-identifier list into raw SQL; additionally, the use of filter_input() bypasses WordPress&amp;#39;s wp_magic_quotes() protection, and the widget_id validation loop is skipped entirely when no valid widget_id is supplied, leaving $isValid at 1. This makes it possible for unauthenticated attackers 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 Sticky Chat Widget plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;scw_form_fields&amp;#39; parameter array keys of the &amp;#39;scw_save_form_data&amp;#39; AJAX action in versions up to, and including, 1.4.2. This is due to the save_form_data() function passing attacker-controlled POST array keys unsanitized to $wpdb-&amp;gt;insert(), which wraps column identifiers in backticks without escaping them, allowing a backtick in an attacker-supplied key to break out of the column-identifier list into raw SQL; additionally, the use of filter_input() bypasses WordPress&amp;#39;s wp_magic_quotes() protection, and the widget_id validation loop is skipped entirely when no valid widget_id is supplied, leaving $isValid at 1. This makes it possible for unauthenticated attackers 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://vulnerability.circl.lu/vuln/ghsa-x4cw-pxp4-3x6g</guid>
    </item>
  </channel>
</rss>
