CVE-2026-17607: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in chuck1982 WP Inventory Manager
The WP Inventory Manager plugin for WordPress is vulnerable to SQL Injection via the 'where' 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->prepare() or a whitelist. The resulting string is concatenated into a raw SELECT statement that is executed via $wpdb->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.
AI Analysis
Technical Summary
The WP Inventory Manager plugin (versions <=2.5.1) suffers from an SQL Injection vulnerability (CWE-89) in the 'where' attribute of the [wpinventory] shortcode. The function WPIMItem::get_all() uses parse_custom_where() which only performs html_entity_decode(), strips semicolons, and replaces field-label names but does not use $wpdb->prepare() or a whitelist to sanitize input. The user-supplied 'where' parameter is concatenated directly into a raw SQL SELECT statement executed by $wpdb->get_results(), enabling authenticated attackers with Contributor-level or higher privileges to append malicious SQL queries and extract sensitive data from the database.
Potential Impact
An attacker with Contributor-level or higher privileges can exploit this vulnerability to perform SQL Injection attacks, allowing unauthorized reading of sensitive information from the database. The vulnerability does not impact integrity or availability but compromises confidentiality. There are no known exploits in the wild as of the publication date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, restrict Contributor-level access and above to trusted users only. Avoid using the vulnerable 'where' shortcode attribute or sanitize inputs manually if possible.
CVE-2026-17607: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in chuck1982 WP Inventory Manager
Description
The WP Inventory Manager plugin for WordPress is vulnerable to SQL Injection via the 'where' 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->prepare() or a whitelist. The resulting string is concatenated into a raw SELECT statement that is executed via $wpdb->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.
CVSS v3.1
Score 6.5medium
Affected software
chuck1982
WP Inventory Manager
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WP Inventory Manager plugin (versions <=2.5.1) suffers from an SQL Injection vulnerability (CWE-89) in the 'where' attribute of the [wpinventory] shortcode. The function WPIMItem::get_all() uses parse_custom_where() which only performs html_entity_decode(), strips semicolons, and replaces field-label names but does not use $wpdb->prepare() or a whitelist to sanitize input. The user-supplied 'where' parameter is concatenated directly into a raw SQL SELECT statement executed by $wpdb->get_results(), enabling authenticated attackers with Contributor-level or higher privileges to append malicious SQL queries and extract sensitive data from the database.
Potential Impact
An attacker with Contributor-level or higher privileges can exploit this vulnerability to perform SQL Injection attacks, allowing unauthorized reading of sensitive information from the database. The vulnerability does not impact integrity or availability but compromises confidentiality. There are no known exploits in the wild as of the publication date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, restrict Contributor-level access and above to trusted users only. Avoid using the vulnerable 'where' shortcode attribute or sanitize inputs manually if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-27T16:53:49.573Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aacec8655bf5e2cf5b113e2
Added to database: 09/18/2026, 07:47:18 UTC
Last enriched: 09/18/2026, 08:02:19 UTC
Last updated: 09/19/2026, 01:16:38 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.