# CVE-2026-76005: WP Inventory Manager <= 2.5.5 - Authenticated (Contributor+) SQL Injection via 'sort_order' Shortcode Attribute


- **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
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-4mfw-7m87-4pf8

## What is CVE-2026-76005?

CVE-2026-76005 is a medium-severity vulnerability in chuck1982 WP Inventory Manager, published on 28 Oct 2026. 

### Official description

The WP Inventory Manager plugin for WordPress is vulnerable to time-based SQL Injection via 'sort_order' Shortcode Attribute in all versions up to, and including, 2.5.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. This can be exploited by a Contributor via the [wpinventory_categories] shortcode embedded in a draft post rendered through preview, without requiring the post to be published.

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

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


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

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

## Is CVE-2026-76005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76005 is a medium-severity vulnerability in chuck1982 WP Inventory Manager, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76005 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-76005/ (Markdown: https://insights.sbomify.com/CVE-2026-76005/index.md)
```

## Sources

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

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