Quick answers
- Is CVE-2026-90599 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90599 being exploited in the wild.
- How severe is CVE-2026-90599?
- Medium severity, with a CVSS score of 4.3, published 13 September 2026.
- Which products and versions are affected?
- Rizwan17 inventory-management-system up to commit 5e74a46b4b70623d0e4a0c9c4aee3bd1777185d2.
- Is there a fix for CVE-2026-90599?
- 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-90599 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-90599?
- 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 is a cross-site request forgery (CSRF) in the includes/process.php file affecting all POST endpoints. The root cause is the absence of CSRF token validation and inadequate authentication checks; the application relies solely on session cookies and never binds state-changing requests to a per-session secret token or implements strict Origin/Referer checks. An attacker can craft a malicious HTML form or fetch request that, when visited by an authenticated user, will be automatically submitted with the victim's session credentials attached by the browser. This allows the attacker to perform actions such as deleting products, adding categories, creating user accounts, or placing orders. No patch has been released; the project uses rolling releases and has not yet responded to the early disclosure.
Affected products
- Rizwan17 inventory-management-system up to commit 5e74a46b4b70623d0e4a0c9c4aee3bd1777185d2
Timeline
- 2026-09-13: disclosed: CVE-2026-90599 published
- 2026-08-03: other: Vulnerability reported via GitHub issue #17