<?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:47:22 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-382165</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-382165</link>
      <description>EUVD-2026-382165</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-382165</guid>
    </item>
    <item>
      <title>fkie_cve-2026-12951</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-12951</link>
      <description>&lt;p&gt;The Dc Woocommerce Multi Vendor plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order_by&amp;#39; parameter of the /multivendorx/v1/compliance/report-abuse REST endpoint in versions up to and including 5.0.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query — the value is concatenated directly into an ORDER BY clause where esc_sql() (which only neutralizes characters needed to break out of quoted string literals) provides no protection. This makes it possible for authenticated attackers, with vendor-level access and above (users granted the &amp;#39;edit_stores&amp;#39; capability), 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 Dc Woocommerce Multi Vendor plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order_by&amp;#39; parameter of the /multivendorx/v1/compliance/report-abuse REST endpoint in versions up to and including 5.0.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query — the value is concatenated directly into an ORDER BY clause where esc_sql() (which only neutralizes characters needed to break out of quoted string literals) provides no protection. This makes it possible for authenticated attackers, with vendor-level access and above (users granted the &amp;#39;edit_stores&amp;#39; capability), 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-12951</guid>
    </item>
    <item>
      <title>GHSA-xgpw-mm25-3whc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xgpw-mm25-3whc</link>
      <description>&lt;p&gt;The Dc Woocommerce Multi Vendor plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order_by&amp;#39; parameter of the /multivendorx/v1/compliance/report-abuse REST endpoint in versions up to and including 5.0.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query — the value is concatenated directly into an ORDER BY clause where esc_sql() (which only neutralizes characters needed to break out of quoted string literals) provides no protection. This makes it possible for authenticated attackers, with vendor-level access and above (users granted the &amp;#39;edit_stores&amp;#39; capability), 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 Dc Woocommerce Multi Vendor plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;order_by&amp;#39; parameter of the /multivendorx/v1/compliance/report-abuse REST endpoint in versions up to and including 5.0.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query — the value is concatenated directly into an ORDER BY clause where esc_sql() (which only neutralizes characters needed to break out of quoted string literals) provides no protection. This makes it possible for authenticated attackers, with vendor-level access and above (users granted the &amp;#39;edit_stores&amp;#39; capability), 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-xgpw-mm25-3whc</guid>
    </item>
  </channel>
</rss>
