Inventree EUVD-2026-16359

Requires authenticated user account on InvenTree versions prior to 1.2.6. Attacker exploits bulk operation API endpoints (/api/part/, /api/stock/, /api/order/so/allocation/, etc.) by crafting filters parameter with Django ORM __ lookup syntax to extract sensitive database information via blind boolean-based queries. No victim interaction needed.

Real-world risk is moderate to high for exposed installations despite the 7.7 CVSS score. The CVSS vector indicates network-accessible exploitation with low attack complexity and no user interaction required, though low-level authentication (PR:L) is necessary, limiting the attack surface to authenticated users or compromised accounts. The changed scope (S:C) and high confidentiality impact (C:H) reflect that attackers can pivot beyond their authorization boundaries to access database information across the entire system. EPSS probability data is not provided in available intelligence. No public exploit code exists and no CISA KEV listing confirms active exploitation, reducing immediate urgency. However, the vulnerability's technical simplicity (direct parameter injection without complex exploitation chains) and the specificity of the GitHub security advisory (GHSA-m8j2-vfmq-p6qg) with accompanying pull request documentation suggest proof-of-concept development would be straightforward for moderately skilled attackers. Organizations running InvenTree with sensitive inventory, supplier, or customer data accessible to low-privilege authenticated users should prioritize patching, as the attack is fully automatable and requires no specialized tools beyond API access.

An authenticated attacker with low-level InvenTree account credentials accesses bulk operation API endpoints such as /api/part/ and crafts malicious filters parameters using Django's relationship traversal syntax (e.g., user__password__startswith). By iterating through boolean queries and observing response differences in returned result sets or timing variations, the attacker systematically extracts sensitive information including user credentials, supplier details, pricing data, or customer information that would normally be restricted by access controls. The attack requires only standard HTTP API access and can be automated with scripting tools, making it feasible for attackers with basic Django ORM knowledge to exfiltrate entire database contents character-by-character through blind inference techniques.