CVE-2026-3725
Lab1024 Smartadmin ≤ 3.29
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-3725 is a medium-severity Incomplete Filtering of Special Elements (CWE-791) vulnerability in Lab1024 Smartadmin. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-3725 is a server-side template injection (SSTI) vulnerability in the 1024-lab/lab1024 SmartAdmin application, affecting versions up to 3.29. The flaw resides in the freemarkerResolverContent function within the file sa-base/src/main/java/net/lab1024/sa/base/module/support/mail/MailService.java, part of the FreeMarker Template Handler component. It stems from improper neutralization of special elements used in a template engine (CWE-791, CWE-1336), triggered by manipulating the template_content argument.
The vulnerability allows remote exploitation by low-privileged users (PR:L), with no need for user interaction (UI:N) and low attack complexity (AC:L). Successful exploitation can result in limited impacts to confidentiality, integrity, and availability (C:L/I:L/A:L), as scored at CVSS 6.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L). Attackers with access to manipulate email template content could inject malicious FreeMarker templates to execute arbitrary code or access sensitive data within the application's context.
Advisories from VulDB and a Notion page detail the SSTI in SmartAdmin's email template rendering but report no patches or mitigations, as the vendor was contacted early without response. Security practitioners should upgrade to newer versions if available, sanitize template inputs, or disable dynamic template rendering in MailService.
An exploit has been publicly disclosed and may be in use, increasing the urgency for affected deployments to assess exposure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10228
Vulnerability Data
A flaw has been found in 1024-lab/lab1024 SmartAdmin up to 3.29. Affected by this issue is the function freemarkerResolverContent of the file sa-base/src/main/java/net/lab1024/sa/base/module/support/mail/MailService.java of the component FreeMarker Template Handler. Executing a manipulation of the argument template_content can lead to improper…
more
neutralization of special elements used in a template engine. The attack can be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.2V1.3.7V1.3.10
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing neutralization of template directives.
Input validation directly requires complete filtering of special elements on received data before further processing or forwarding.
Security engineering principles require use of safe templating APIs and proper escaping of external input.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require complete input filtering and sanitization to prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect incomplete filtering but does not itself implement the filtering.
Secure development life cycle processes include validation activities that reduce the likelihood of CWE-791 but do not specify the control itself.
Application security requirements explicitly call for input validation and sanitization that directly mitigates incomplete special-element filtering.
Secure system architecture and engineering principles require defensive design patterns that prevent unfiltered data from reaching downstream components.
Secure coding standards mandate complete filtering and escaping of special elements, directly eliminating CWE-791.