Smarty before 4.5.8 and 5.x before 5.8.5 contains a code injection vulnerability where the top-level nocache_hash is never restored during extends:/multi-component template inheritance, leaving it null. Attackers can supply assigned data containing a forged SmartyNocache marker t...
Product
ubuntu/smarty3 vulnerabilities
16 published CVES affecting ubuntu/smarty3, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 16
- Critical
- 3
- High
- 7
- Medium
- 6
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest ubuntu/smarty3 CVEs
Newest publication first
-
CriticalCVSS 9.2 EPSS 0.82%
-
MediumCVSS 6.9 EPSS 0.57%
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 4.5.7 and 5.8.2, depending on the release line, Smarty's {fetch} handling in libs/plugins/function.fetch.php and src/FunctionHandler/Fetch.php used Securit...
-
MediumCVSS 6.9 EPSS 0.51%
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a te...
-
MediumCVSS 6.9 EPSS 0.53%
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 5.8.2 (and 4.5.7 on the 4.x line), Security::_checkDir() does not fully resolve symbolic links before validating that a requested path lies within a config...
-
HighCVSS 7.3 EPSS 0.51%
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. In affected versions template authors could inject php code by choosing a malicious file name for an extends-tag. Sites that cannot fully trust template authors sho...
-
MediumCVSS 6.1 EPSS 1.0% PoC
Smarty is a template engine for PHP. In affected versions smarty did not properly escape javascript code. An attacker could exploit this vulnerability to execute arbitrary JavaScript code in the context of the user's browser session. This may lead to unauthorized access to sensit...
-
CVE-2018-25047 Smarty Cross-site Scripting vulnerability in pages that use smarty_function_mailto
PublishedMediumCVSS 5.4 EPSS 1.2% PoCIn Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mailto.php allows XSS. A web page that uses smarty_function_mailto, and that could be parameterized using GET or POST input parameters, could allow injection of JavaScript code by a user.
-
HighCVSS 8.8 EPSS 4.9% PoC
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.45 and 4.1.1, template authors could inject php code by choosing a malicious {block} name or {include} file name. Sites that cannot fully trus...
-
HighCVSS 8.8 EPSS 2.1% PoC
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.43 and 4.0.3, template authors could run restricted static php methods. Users should upgrade to version 3.1.43 or 4.0.3 to receive a patch.
-
HighCVSS 8.8 EPSS 1.9% PoC
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.42 and 4.0.2, template authors could run arbitrary PHP code by crafting a malicious math string. If a math string was passed through as user p...
-
CriticalCVSS 9.8 EPSS 82.3% PoC
Smarty before 3.1.39 allows code injection via an unexpected function name after a {function name= substring.
-
HighCVSS 7.5 EPSS 8.5% PoC
Smarty before 3.1.39 allows a Sandbox Escape because $smarty.template_object can be accessed in sandbox mode.
-
HighCVSS 7.5 EPSS 3.5% PoC
Smarty_Security::isTrustedResourceDir() in Smarty before 3.1.33 is prone to a path traversal vulnerability due to insufficient template code sanitization. This allows attackers controlling the executed template code to bypass the trusted directory security restriction and read ar...
-
MediumCVSS 5.9 EPSS 2.7% PoC
Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:./../ substring in an include statement.
-
CriticalCVSS 9.8 EPSS 3.1%
Smarty 3 before 3.1.32 is vulnerable to a PHP code injection when calling fetch() or display() functions on custom resources that does not sanitize template name.
-
HighCVSS 7.5 EPSS 3.1%
Smarty before 3.1.21 allows remote attackers to bypass the secure mode restrictions and execute arbitrary PHP code as demonstrated by "{literal}<{/literal}script language=php>" in a template.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.