<?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:30:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-19800 — Mail Mint &lt;= 1.31.0 - Authenticated (Custom+) SQL Injection via 'status' Parameter</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-19800</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getwpfunnels Mail Mint – Email Marketing, Newsletter, Email Automation &amp;amp; WooCommerce Emails&lt;/p&gt;
&lt;p&gt;The Mail Mint – Email Marketing, Newsletter, Email Automation &amp;amp; WooCommerce Emails plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;status&amp;#39; parameter in all versions up to, and including, 1.31.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. The $wpdb-&amp;gt;prepare() call does not protect against this injection because the attacker-controlled $contact_filter_query fragment is concatenated into the SQL format string before prepare() executes — prepare() only processes %s/%d placeholders and cannot sanitize content already embedded in the format string. REST API JSON bodies are parsed from php://input and bypass WordPress&amp;#39;s wp_magic_quotes(), meaning double-quote characters in status array values reach the SQL sink unescaped. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The required &amp;#39;mint_read_contacts&amp;#39; capability is a plugin-specific capability not assigned to any default WordPress role; it must be explicitly granted by an administrator, making this effectively an Administrator+ vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getwpfunnels Mail Mint – Email Marketing, Newsletter, Email Automation &amp;amp; WooCommerce Emails&lt;/p&gt;
&lt;p&gt;The Mail Mint – Email Marketing, Newsletter, Email Automation &amp;amp; WooCommerce Emails plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;status&amp;#39; parameter in all versions up to, and including, 1.31.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. The $wpdb-&amp;gt;prepare() call does not protect against this injection because the attacker-controlled $contact_filter_query fragment is concatenated into the SQL format string before prepare() executes — prepare() only processes %s/%d placeholders and cannot sanitize content already embedded in the format string. REST API JSON bodies are parsed from php://input and bypass WordPress&amp;#39;s wp_magic_quotes(), meaning double-quote characters in status array values reach the SQL sink unescaped. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The required &amp;#39;mint_read_contacts&amp;#39; capability is a plugin-specific capability not assigned to any default WordPress role; it must be explicitly granted by an administrator, making this effectively an Administrator+ vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-19800</guid>
    </item>
  </channel>
</rss>
