# CVE-2026-17607: WP Inventory Manager <= 2.5.1 - Authenticated (Contributor+) SQL Injection via 'where' Shortcode Attribute

> Authenticated attackers with Contributor access can exploit SQL injection in the WP Inventory Manager plugin to extract sensitive database information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-q2g2-xwwx-rp3m

## What is CVE-2026-17607?

CVE-2026-17607 is a medium-severity SQL injection vulnerability in chuck1982 WP Inventory Manager, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-17607?


## How do I fix CVE-2026-17607?

No fix has been published for CVE-2026-17607 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17607 being exploited?

There is no known exploitation of CVE-2026-17607 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17607 and fix it if it is affected.

What it is: CVE-2026-17607 is a medium-severity SQL injection vulnerability in chuck1982 WP Inventory Manager, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17607 in the wild and no public exploit code.

Affected product: chuck1982 WP Inventory Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17607/ (Markdown: https://insights.sbomify.com/CVE-2026-17607/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17607
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17607
- OSV: https://osv.dev/vulnerability/CVE-2026-17607

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17607/
Summaries are generated and may contain mistakes; the official description above is the record.