<?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>Mon, 28 Sep 2026 12:35:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-17607 — WP Inventory Manager &lt;= 2.5.1 - Authenticated (Contributor+) SQL Injection via 'where' Shortcode Attribute</title>
      <link>https://db.gcve.eu/vuln/cve-2026-17607</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; chuck1982 WP Inventory Manager&lt;/p&gt;
&lt;p&gt;The WP Inventory Manager plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;where&amp;#39; shortcode attribute of the [wpinventory] shortcode in versions up to, and including, 2.5.1. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query in the WPIMItem::get_all() function — parse_custom_where() only performs html_entity_decode(), strips semicolons, and does field-label name replacements, without using $wpdb-&amp;gt;prepare() or a whitelist. The resulting string is concatenated into a raw SELECT statement that is executed via $wpdb-&amp;gt;get_results(). This makes it possible for authenticated attackers, with Contributor-level access and above, 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;&lt;strong&gt;Affected:&lt;/strong&gt; chuck1982 WP Inventory Manager&lt;/p&gt;
&lt;p&gt;The WP Inventory Manager plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;where&amp;#39; shortcode attribute of the [wpinventory] shortcode in versions up to, and including, 2.5.1. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query in the WPIMItem::get_all() function — parse_custom_where() only performs html_entity_decode(), strips semicolons, and does field-label name replacements, without using $wpdb-&amp;gt;prepare() or a whitelist. The resulting string is concatenated into a raw SELECT statement that is executed via $wpdb-&amp;gt;get_results(). This makes it possible for authenticated attackers, with Contributor-level access and above, 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://db.gcve.eu/vuln/cve-2026-17607</guid>
    </item>
  </channel>
</rss>
