The vulnerability arises from an unsanitized Jinja2 template rendering of custom part name formats in InvenTree. Although a previous fix introduced a sandboxed environment for validation, the production renderer continued to use the standard, insecure Jinja2 environment. This mismatch allows a staff member with settings access to supply a template that passes validation yet contains expressions that execute arbitrary code during actual rendering. The result is remote code execution within the application’s context, potentially granting full control over the underlying system. The weakness corresponds to the specified CWE for insecure implementation of a sandboxed environment.

InvenTree editions from version 1.2.3 up to and including 1.2.6 are impacted. The security issue was addressed in releases 1.2.7 and 1.3.0. The platform is an open‑source inventory management system, accessible to users with administrative privileges. No other vendors or product lines are listed within the vulnerability statement.

The CVSS score of 5.5 places the vulnerability in the medium severity range, while the EPSS score is not available and the flaw is not currently cataloged in CISA’s KEV list. The likely attack vector is an internal privilege escalation, as exploitation requires a staff user with permission to modify system settings. If such access is obtained, the attacker can execute arbitrary code, impacting confidentiality, integrity, and availability. Although no public exploits have been reported yet, the combination of a known weakness, moderate severity, and required privileged access suggests a moderate to high risk for organizations running vulnerable InvenTree instances without timely remediation.