Smarty
By the Year
In 2024 there have been 0 vulnerabilities in Smarty . Last year Smarty had 2 security vulnerabilities published. Right now, Smarty is on track to have less security vulnerabilities in 2024 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 2 | 5.45 |
| 2022 | 4 | 7.95 |
| 2021 | 2 | 8.65 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 2 | 6.70 |
It may take a day or so for new Smarty vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Smarty Security Vulnerabilities
Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerabili
CVE-2023-41661
4.8 - Medium
- September 29, 2023
Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in PressPage Entertainment Inc. Smarty for WordPress plugin <= 3.1.35 versions.
XSS
Smarty is a template engine for PHP
CVE-2023-28447
6.1 - Medium
- March 28, 2023
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 sensitive user data, manipulation of the web application's behavior, or unauthorized actions performed on behalf of the user. Users are advised to upgrade to either version 3.1.48 or to 4.3.1 to resolve this issue. There are no known workarounds for this vulnerability.
XSS
In Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mailto.php allows XSS
CVE-2018-25047
5.4 - Medium
- September 15, 2022
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 could be parameterized using GET or POST input parameters, could allow injection of JavaScript code by a user.
XSS
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic
CVE-2022-29221
8.8 - High
- May 24, 2022
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 trust template authors should upgrade to versions 3.1.45 or 4.1.1 to receive a patch for this issue. There are currently no known workarounds.
Code Injection
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic
CVE-2021-29454
8.8 - High
- January 10, 2022
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 provided data to the math function, external users could run arbitrary PHP code by crafting a malicious math string. Users should upgrade to version 3.1.42 or 4.0.2 to receive a patch.
Injection
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic
CVE-2021-21408
8.8 - High
- January 10, 2022
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.
Improper Input Validation
Smarty before 3.1.39
CVE-2021-26119
7.5 - High
- February 22, 2021
Smarty before 3.1.39 allows a Sandbox Escape because $smarty.template_object can be accessed in sandbox mode.
Smarty before 3.1.39
CVE-2021-26120
9.8 - Critical
- February 22, 2021
Smarty before 3.1.39 allows code injection via an unexpected function name after a {function name= substring.
Code Injection
Smarty_Security::isTrustedResourceDir() in Smarty before 3.1.33 is prone to a path traversal vulnerability due to insufficient template code sanitization
CVE-2018-13982
7.5 - High
- September 18, 2018
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 arbitrary files.
Directory traversal
Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:
CVE-2018-16831
5.9 - Medium
- September 11, 2018
Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:./../ substring in an include statement.
Directory traversal
PHP remote file inclusion vulnerability in unit_test/test_cases.php in Smarty 2.6.1
CVE-2006-7193
- April 12, 2007
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 in the SMARTY_DIR parameter. NOTE: this issue is disputed by CVE and a third party because SMARTY_DIR is a constant
PHP remote file inclusion vulnerability in libs/Smarty.class.php in Smarty 2.6.9
CVE-2006-7105
- March 03, 2007
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 the filename parameter. NOTE: in the original disclosure, filename is used in a function definition, so this report is probably incorrect
Code Injection
