Quick answers
- Is CVE-2026-87921 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87921 being exploited in the wild.
- How severe is CVE-2026-87921?
- High severity, with a CVSS score of 7.3, published 9 September 2026.
- Which products and versions are affected?
- Rizwan17 inventory-management-system up to bfe78a330d01bb26b9daec5dc9ecd5c77900e03f.
- Is there a fix for CVE-2026-87921?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-87921 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-87921?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the update_record() function in includes/manage.php, which constructs UPDATE SQL statements by string concatenation of unsanitized POST parameters into the SET and WHERE clauses. The update_category, update_brand, and update_product handlers in includes/process.php expose this function without authentication. An attacker can inject SQL metacharacters (quotes, semicolons, comments) via POST parameters like update_category or cid to break out of string literals and rewrite the WHERE clause, enabling updates to unintended rows or even lateral pivots to other database tables. The attack is remotely exploitable with no prerequisites; exploit code is publicly available. No patch has been issued.
Affected products
- Rizwan17 inventory-management-system up to bfe78a330d01bb26b9daec5dc9ecd5c77900e03f
Timeline
- 2026-07-30: disclosed: SQL injection vulnerability reported via GitHub issue #9
- 2026-09-09: advisory: CVE-2026-87921 published on NVD