Search for packages
| purl | pkg:composer/smarty/smarty@4.1.1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3829-yarc-yqh3
Aliases: CVE-2023-28447 GHSA-7j98-h7fp-4vwj |
smarty Cross-site Scripting vulnerability in Javascript escaping 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. |
Affected by 1 other vulnerability. |
|
VCID-a3yk-8fmf-x7fw
Aliases: CVE-2024-35226 GHSA-4rmg-292m-wg3w |
Smarty vulnerable to PHP Code Injection by malicious attribute in extends-tag Template authors could inject php code by choosing a malicous file name for an extends-tag. Users that cannot fully trust template authors should update asap. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-h2k4-cqfq-sbhw
Aliases: CVE-2018-25047 GHSA-hwq7-5vv9-c6cf |
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. |
Affected by 2 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-4dmb-dnk6-6qdd | 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. |
CVE-2022-29221
GHSA-634x-pc3q-cf4c |