CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVE-2026-57853
High (8.7).
DataGerry before 3.3.0 contains a server-side template injection vulnerability that allows authenticated attackers with base.docapi.template.add permission to store arbitrary Jinja2 payloads in the template_data field via POST /rest/docapi/template, which is later rendered in a non-sandboxed Jinja2 environment when a user calls GET /rest/docapi/template/<id>/render/<object_id>. Attackers can exploit the standard cycler.__init__.__globals__.os gadget chain to execute arbitrary operating system commands as the DataGerry web process user, confirmed as root in default Docker deployments, achieving remote code execution.
Severity
CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- CWEs
- CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
CWE-1336 Improper Neutralization of Special Elements Used in a Template Engine - OWASP Top 10
- A05:2025 Injection
- Published
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-57853 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57853?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57853?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-57853 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| DataGerry | before 3.3.0 |
Attack patterns (CAPEC)
- CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
- CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
- CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
- CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
- CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
- CAPEC-592 Stored XSS Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.