<?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>Mon, 05 Oct 2026 18:12:45 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-319671</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-319671</link>
      <description>EUVD-2026-319671</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-319671</guid>
    </item>
    <item>
      <title>fkie_cve-2026-9065</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-9065</link>
      <description>&lt;p&gt;SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters (&amp;#39;model_name&amp;#39;, &amp;#39;model_id&amp;#39;, &amp;#39;integration_id&amp;#39;, &amp;#39;provider&amp;#39;) on the REST API endpoint &amp;#39;/surecart/v1/integrations/{id}&amp;#39;.&lt;/p&gt;
&lt;p&gt;The root cause is a flawed escaping bypass in the query builder (&amp;#39;wp-query-builder&amp;#39;). Values passed to the &amp;#39;where()&amp;#39; method are only sanitized via &amp;#39;$wpdb-&amp;gt;prepare()&amp;#39; when they do **not** contain a dot (&amp;#39;.&amp;#39;) or the WordPress table prefix (&amp;#39;wp_&amp;#39;). By including a dot anywhere in the payload, an attacker completely bypasses the escaping logic and injects arbitrary SQL into the &amp;#39;WHERE&amp;#39; clause, allowing full UNION-based extraction of the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters (&amp;#39;model_name&amp;#39;, &amp;#39;model_id&amp;#39;, &amp;#39;integration_id&amp;#39;, &amp;#39;provider&amp;#39;) on the REST API endpoint &amp;#39;/surecart/v1/integrations/{id}&amp;#39;.&lt;/p&gt;
&lt;p&gt;The root cause is a flawed escaping bypass in the query builder (&amp;#39;wp-query-builder&amp;#39;). Values passed to the &amp;#39;where()&amp;#39; method are only sanitized via &amp;#39;$wpdb-&amp;gt;prepare()&amp;#39; when they do **not** contain a dot (&amp;#39;.&amp;#39;) or the WordPress table prefix (&amp;#39;wp_&amp;#39;). By including a dot anywhere in the payload, an attacker completely bypasses the escaping logic and injects arbitrary SQL into the &amp;#39;WHERE&amp;#39; clause, allowing full UNION-based extraction of the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-9065</guid>
    </item>
    <item>
      <title>GHSA-qp65-j7f9-qv73</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qp65-j7f9-qv73</link>
      <description>&lt;p&gt;SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters (&amp;#39;model_name&amp;#39;, &amp;#39;model_id&amp;#39;, &amp;#39;integration_id&amp;#39;, &amp;#39;provider&amp;#39;) on the REST API endpoint &amp;#39;/surecart/v1/integrations/{id}&amp;#39;.&lt;/p&gt;
&lt;p&gt;The root cause is a flawed escaping bypass in the query builder (&amp;#39;wp-query-builder&amp;#39;). Values passed to the &amp;#39;where()&amp;#39; method are only sanitized via &amp;#39;$wpdb-&amp;gt;prepare()&amp;#39; when they do **not** contain a dot (&amp;#39;.&amp;#39;) or the WordPress table prefix (&amp;#39;wp_&amp;#39;). By including a dot anywhere in the payload, an attacker completely bypasses the escaping logic and injects arbitrary SQL into the &amp;#39;WHERE&amp;#39; clause, allowing full UNION-based extraction of the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SureCart version prior to 4.2.1 are vulnerable to authenticated SQL injection via multiple parameters (&amp;#39;model_name&amp;#39;, &amp;#39;model_id&amp;#39;, &amp;#39;integration_id&amp;#39;, &amp;#39;provider&amp;#39;) on the REST API endpoint &amp;#39;/surecart/v1/integrations/{id}&amp;#39;.&lt;/p&gt;
&lt;p&gt;The root cause is a flawed escaping bypass in the query builder (&amp;#39;wp-query-builder&amp;#39;). Values passed to the &amp;#39;where()&amp;#39; method are only sanitized via &amp;#39;$wpdb-&amp;gt;prepare()&amp;#39; when they do **not** contain a dot (&amp;#39;.&amp;#39;) or the WordPress table prefix (&amp;#39;wp_&amp;#39;). By including a dot anywhere in the payload, an attacker completely bypasses the escaping logic and injects arbitrary SQL into the &amp;#39;WHERE&amp;#39; clause, allowing full UNION-based extraction of the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qp65-j7f9-qv73</guid>
    </item>
  </channel>
</rss>
