Quick answers
- Is CVE-2026-87923 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87923 being exploited in the wild.
- How severe is CVE-2026-87923?
- Medium severity, with a CVSS score of 4.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-87923?
- 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-87923 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-87923?
- 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
This is a stored cross-site scripting (XSS) vulnerability in the List Handler component (includes/DBOperation.php and includes/process.php) of the inventory management system. The vulnerability stems from missing output encoding when displaying inventory names (category_name, brand_name, product_name) in HTML table cells and option labels. User input submitted via unauthenticated POST endpoints is stored in the database without sanitization and later rendered directly into HTML without htmlspecialchars() or equivalent encoding. An attacker can craft a malicious payload (e.g., <script>alert(/XSS/)</script>) and submit it through the brand/category/product creation endpoints, which are accessible without authentication. When legitimate users load the management interface, the malicious script executes in their browser context, enabling session hijacking or administrative impersonation.
Affected products
- Rizwan17 inventory-management-system up to bfe78a330d01bb26b9daec5dc9ecd5c77900e03f
Timeline
- 2026-07-30: disclosed: Vulnerability reported via GitHub issue #12
- 2026-09-09: advisory: CVE-2026-87923 published