<?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://db.gcve.eu</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>Wed, 21 Oct 2026 17:08:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-92766 — Vitepos &lt;= 3.5.1 - Unauthenticated SQL Injection via 'src_by' Parameter</title>
      <link>https://db.gcve.eu/vuln/cve-2026-92766</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; appsbd Vitepos – Point of Sale (POS) for WooCommerce&lt;/p&gt;
&lt;p&gt;The Vitepos – Point of Sale (POS) for WooCommerce plugin for WordPress is vulnerable to generic SQL Injection via the &amp;#39;src_by&amp;#39; parameter in all versions up to, and including, 3.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. This makes it possible for unauthenticated attackers, or authenticated attackers holding any POS role (such as vtpos-cashier), to exploit the vulnerability, as the /vitepos/v1/vendor/list REST route&amp;#39;s permission callback requires only a POS role assignment rather than any elevated WordPress capability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; appsbd Vitepos – Point of Sale (POS) for WooCommerce&lt;/p&gt;
&lt;p&gt;The Vitepos – Point of Sale (POS) for WooCommerce plugin for WordPress is vulnerable to generic SQL Injection via the &amp;#39;src_by&amp;#39; parameter in all versions up to, and including, 3.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. This makes it possible for unauthenticated attackers, or authenticated attackers holding any POS role (such as vtpos-cashier), to exploit the vulnerability, as the /vitepos/v1/vendor/list REST route&amp;#39;s permission callback requires only a POS role assignment rather than any elevated WordPress capability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-92766</guid>
    </item>
  </channel>
</rss>
