FKIE_CVE-2026-27629
Vulnerability from fkie_nvd - Published: 2026-02-25 03:16 - Updated: 2026-02-27 20:00
Severity ?
5.9 (Medium) - CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
8.8 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
8.8 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Summary
InvenTree is an Open Source Inventory Management System. Prior to version 1.2.3, insecure server-side templates can be hijacked to expose secure information to the client. When generating custom batch codes, the InvenTree server makes use of a customizable jinja2 template, which can be modified by a staff user to exfiltrate sensitive information or perform code execution on the server. This issue requires access by a user with granted staff permissions, followed by a request to generate a custom batch code via the API. Once the template has been modified in a malicious manner, the API call to generate a new batch code could be made by other users, and the template code will be executed with their user context. The code has been patched to ensure that all template generation is performed within a secure sandboxed context. This issue has been addressed in version 1.2.3, and any versions from 1.3.0 onwards. Some workarounds are available. The batch code template is a configurable global setting which can be adjusted via any user with staff access. To prevent this setting from being edited, it can be overridden at a system level to a default value, preventing it from being edited. This requires system administrator access, and cannot be changed from the client side once the server is running. It is recommended that for InvenTree installations prior to 1.2.3 the `STOCK_BATCH_CODE_TEMPLATE` and `PART_NAME_FORMAT` global settings are overridden at the system level to prevent editing.
References
| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m | Mitigation, Vendor Advisory |
Impacted products
| Vendor | Product | Version | |
|---|---|---|---|
| inventree_project | inventree | * |
{
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:inventree_project:inventree:*:*:*:*:*:*:*:*",
"matchCriteriaId": "B9F4ACA8-A3F6-4A3D-A434-DAAF703DEE40",
"versionEndExcluding": "1.2.3",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "InvenTree is an Open Source Inventory Management System. Prior to version 1.2.3, insecure server-side templates can be hijacked to expose secure information to the client. When generating custom batch codes, the InvenTree server makes use of a customizable jinja2 template, which can be modified by a staff user to exfiltrate sensitive information or perform code execution on the server. This issue requires access by a user with granted staff permissions, followed by a request to generate a custom batch code via the API. Once the template has been modified in a malicious manner, the API call to generate a new batch code could be made by other users, and the template code will be executed with their user context. The code has been patched to ensure that all template generation is performed within a secure sandboxed context. This issue has been addressed in version 1.2.3, and any versions from 1.3.0 onwards. Some workarounds are available. The batch code template is a configurable global setting which can be adjusted via any user with staff access. To prevent this setting from being edited, it can be overridden at a system level to a default value, preventing it from being edited. This requires system administrator access, and cannot be changed from the client side once the server is running. It is recommended that for InvenTree installations prior to 1.2.3 the `STOCK_BATCH_CODE_TEMPLATE` and `PART_NAME_FORMAT` global settings are overridden at the system level to prevent editing."
},
{
"lang": "es",
"value": "InvenTree es un Sistema de Gesti\u00f3n de Inventario de C\u00f3digo Abierto. Antes de la versi\u00f3n 1.2.3, las plantillas inseguras del lado del servidor pueden ser secuestradas para exponer informaci\u00f3n segura al cliente. Al generar c\u00f3digos de lote personalizados, el servidor InvenTree utiliza una plantilla jinja2 personalizable, que puede ser modificada por un usuario del personal para exfiltrar informaci\u00f3n sensible o realizar ejecuci\u00f3n de c\u00f3digo en el servidor. Este problema requiere acceso por parte de un usuario con permisos de personal concedidos, seguido de una solicitud para generar un c\u00f3digo de lote personalizado a trav\u00e9s de la API. Una vez que la plantilla ha sido modificada de manera maliciosa, otros usuarios podr\u00edan llamar a la API para generar un nuevo c\u00f3digo de lote, y el c\u00f3digo de la plantilla se ejecutar\u00e1 con su contexto de usuario. El c\u00f3digo ha sido parcheado para asegurar que toda la generaci\u00f3n de plantillas se realice dentro de un contexto seguro en un entorno aislado. Este problema ha sido abordado en la versi\u00f3n 1.2.3, y en cualquier versi\u00f3n a partir de la 1.3.0. Hay disponibles algunas soluciones alternativas. La plantilla de c\u00f3digo de lote es una configuraci\u00f3n global configurable que puede ser ajustada por cualquier usuario con acceso de personal. Para evitar que esta configuraci\u00f3n sea editada, puede ser anulada a nivel de sistema a un valor predeterminado, evitando que sea editada. Esto requiere acceso de administrador de sistema, y no puede ser cambiado desde el lado del cliente una vez que el servidor est\u00e1 en funcionamiento. Se recomienda que para las instalaciones de InvenTree anteriores a la 1.2.3, se anulen las configuraciones globales \u0027STOCK_BATCH_CODE_TEMPLATE\u0027 y \u0027PART_NAME_FORMAT\u0027 a nivel de sistema para evitar su edici\u00f3n."
}
],
"id": "CVE-2026-27629",
"lastModified": "2026-02-27T20:00:51.417",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 3.7,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2026-02-25T03:16:06.680",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-1336"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…