{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33530 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33530 is a high-severity SQL injection vulnerability in InvenTree, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33530 and fix it if it is affected.\n\nWhat it is: CVE-2026-33530 is a high-severity SQL injection vulnerability in InvenTree, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33530 in the wild and no public exploit code.\n\nAffected product: InvenTree. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33530/ (Markdown: https://insights.sbomify.com/CVE-2026-33530/index.md)","id":"CVE-2026-33530","markdown":"https://insights.sbomify.com/CVE-2026-33530/index.md","name":"CVE-2026-33530","record":{"aliases":["GHSA-m8j2-vfmq-p6qg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Inventory Management System","requires_auth":"low_privilege","summary":"Authenticated users can exploit unvalidated ORM filters in InvenTree API endpoints to extract sensitive database information via blind boolean-based injection.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"inventree","vendor":"inventree_project"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-202","name":"Exposure of Sensitive Information Through Data Queries"}],"description":"InvenTree is an Open Source Inventory Management System. Prior to version 1.2.6, certain API endpoints associated with bulk data operations can be hijacked to exfiltrate sensitive information from the database. The bulk operation API endpoints (e.g. `/api/part/`, `/api/stock/`, `/api/order/so/allocation/`, and others) accept a filters parameter that is passed directly to Django's ORM queryset.filter(**filters) without any field allowlisting. This enables any authenticated user to traverse model relationships using Django's __ lookup syntax and perform blind boolean-based data extraction. This issue is patched in version 1.2.6, and 1.3.0 (or above). Users should update to the patched versions. No known workarounds are available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"InvenTree Vulnerable to ORM Filter Injection","id":"CVE-2026-33530","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"InvenTree has Path Traversal In Report Templates","id":"CVE-2026-33531"},"packages":[],"prev":{"headline":"Zoraxy: Authenticated Path Traversal in Config Import leads to RCE","id":"CVE-2026-33529"},"products":["InvenTree"],"published":"2026-03-26","related":[{"cvss_score":9,"headline":"Unrestricted Upload of File with Dangerous Type in inventree/inventree","id":"CVE-2022-2111","kev_date_added":null,"published":"2022-06-17"},{"cvss_score":9,"headline":"Improper Neutralization of Formula Elements in a CSV File in inventree/inventree","id":"CVE-2022-2112","kev_date_added":null,"published":"2022-06-17"},{"cvss_score":8.4,"headline":"Cross-site Scripting (XSS) - Stored in inventree/inventree","id":"CVE-2022-2113","kev_date_added":null,"published":"2022-06-17"},{"cvss_score":8.3,"headline":"InvenTree has Arbitrary API Token Creation","id":"CVE-2026-35478","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) - Stored in inventree/inventree","id":"CVE-2022-3355","kev_date_added":null,"published":"2022-09-29"},{"cvss_score":7.3,"headline":"Stored Cross-site Scripting Vulnerability in Markdown Editor","id":"CVE-2024-47610","kev_date_added":null,"published":"2024-10-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["inventree"]},"summary":"Authenticated users can exploit unvalidated ORM filters in InvenTree API endpoints to extract sensitive database information via blind boolean-based injection.","url":"https://insights.sbomify.com/CVE-2026-33530/"}