Smarty
31 vulnerabilities.
All published vulnerabilities with a CVE number in Smarty products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2023-41661 | Smarty: Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in PressPage Entertainment Inc. Smarty for WordPress plugin <= 3.1.35 versions. | 2023-09-29 | 5.9 |
| CVE-2023-28447 | Smarty: Smarty is a template engine for PHP. In affected versions smarty did not properly escape javascript code. An attacker could exploit this … | 2023-03-28 | 7.1 |
| CVE-2022-29221 | Smarty: Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.45 and … | 2022-05-24 | 8.8 |
| CVE-2021-29454 | Smarty: Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.42 and … | 2022-01-10 | 8.1 |
| CVE-2021-26120 | Smarty: Smarty before 3.1.39 allows code injection via an unexpected function name after a {function name= substring. | 2021-02-22 | 9.8 |
| CVE-2021-26119 | Smarty: Smarty before 3.1.39 allows a Sandbox Escape because $smarty.template_object can be accessed in sandbox mode. | 2021-02-22 | 7.5 |
| CVE-2021-21408 | Smarty: Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.43 and … | 2022-01-10 | 8.8 |
| CVE-2018-25047 | Smarty: In 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 … | 2022-09-14 | 5.4 |
| CVE-2018-16831 | Smarty: Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:./../ substring in an include statement. | 2018-09-11 | 5.9 |
| CVE-2018-13982 | Smarty: Smarty_Security::isTrustedResourceDir() in Smarty before 3.1.33 is prone to a path traversal vulnerability due to insufficient template code … | 2018-09-18 | 7.5 |
| CVE-2017-1000480 | Smarty: 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 … | 2018-01-03 | 9.8 |
| CVE-2014-8350 | Smarty: Smarty before 3.1.21 allows remote attackers to bypass the secure mode restrictions and execute arbitrary PHP code as demonstrated by … | 2014-11-03 | 7.5 |
| CVE-2012-4437 | Smarty: Cross-site scripting (XSS) vulnerability in the SmartyException class in Smarty (aka smarty-php) before 3.1.12 allows remote attackers to inject … | 2012-10-01 | 4.3 |
| CVE-2012-4277 | Smarty: Cross-site scripting (XSS) vulnerability in the smarty_function_html_options_optoutput function in … | 2012-08-13 | 4.3 |
| CVE-2011-1028 | Smarty: The $smarty.template variable in Smarty3 allows attackers to possibly execute arbitrary PHP code via the … | 2019-11-20 | 9.8 |
| CVE-2010-4727 | Smarty: Smarty before 3.0.0 beta 7 does not properly handle the <?php and ?> tags, which has unspecified impact and remote attack vectors. | 2011-02-03 | 10.0 |
| CVE-2010-4726 | Smarty: Unspecified vulnerability in the math plugin in Smarty before 3.0.0 RC1 has unknown impact and remote attack vectors. NOTE: this might overlap … | 2011-02-03 | 10.0 |
| CVE-2010-4725 | Smarty: Smarty before 3.0.0 RC3 does not properly handle an on value of the asp_tags option in the php.ini file, which has unspecified impact and remote … | 2011-02-03 | 10.0 |
| CVE-2010-4724 | Smarty: Multiple unspecified vulnerabilities in the parser implementation in Smarty before 3.0.0 RC3 have unknown impact and remote attack vectors. | 2011-02-03 | 10.0 |
| CVE-2010-4723 | Smarty: Smarty before 3.0.0, when security is enabled, does not prevent access to the (1) dynamic and (2) private object members of an assigned object, … | 2011-02-03 | 9.3 |
| CVE-2010-4722 | Smarty: Unspecified vulnerability in the fetch plugin in Smarty before 3.0.2 has unknown impact and remote attack vectors. | 2011-02-03 | 10.0 |
| CVE-2009-5054 | Smarty: Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended … | 2011-02-03 | 7.5 |
| CVE-2009-5053 | Smarty: Unspecified vulnerability in Smarty before 3.0.0 beta 6 allows remote attackers to execute arbitrary PHP code by injecting this code into a cache … | 2011-02-03 | 7.5 |
| CVE-2009-5052 | Smarty: Multiple unspecified vulnerabilities in Smarty before 3.0.0 beta 6 have unknown impact and attack vectors. | 2011-02-03 | 10.0 |
| CVE-2009-1669 | Smarty: The smarty_function_math function in libs/plugins/function.math.php in Smarty 2.6.22 allows context-dependent attackers to execute arbitrary … | 2009-05-18 | 10.0 |
| CVE-2008-4811 | Smarty: The _expand_quoted_text function in libs/Smarty_Compiler.class.php in Smarty 2.6.20 r2797 and earlier allows remote attackers to execute arbitrary … | 2008-10-31 | 7.5 |
| CVE-2008-4810 | Smarty: The _expand_quoted_text function in libs/Smarty_Compiler.class.php in Smarty 2.6.20 before r2797 allows remote attackers to execute arbitrary PHP … | 2008-10-31 | 7.5 |
| CVE-2008-1066 | Smarty: The modifier.regex_replace.php plugin in Smarty before 2.6.19, as used by Serendipity (S9Y) and other products, allows attackers to call arbitrary … | 2008-02-28 | 7.5 |
| CVE-2006-7193 | Smarty: PHP remote file inclusion vulnerability in unit_test/test_cases.php in Smarty 2.6.1 allows remote attackers to execute arbitrary PHP code via a URL … | 2007-04-12 | 7.5 |
| CVE-2006-7105 | Smarty: PHP remote file inclusion vulnerability in libs/Smarty.class.php in Smarty 2.6.9 allows remote attackers to execute arbitrary PHP code via a URL in … | 2007-03-03 | 9.8 |
| CVE-2005-0913 | Smarty: Unknown vulnerability in the regex_replace modifier (modifier.regex_replace.php) in Smarty before 2.6.8 allows attackers to execute arbitrary PHP … | 2005-05-02 | 7.5 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.