PHP Code Injection by malicious block or filename in Smarty
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 4.9%
exploitation probability
4.9%top 9% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
smarty-php · smartyReferences
https://github.com/smarty-php/smarty/commit/64ad6442ca1da31cefdab5c9874262b702cccdddhttps://github.com/smarty-php/smarty/releases/tag/v3.1.45https://github.com/smarty-php/smarty/releases/tag/v4.1.1https://github.com/smarty-php/smarty/security/advisories/GHSA-634x-pc3q-cf4chttps://lists.debian.org/debian-lts-announce/2022/05/msg00044.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BRAJVDRGCIY5UZ2PQHKDTT7RMKG6WJQQ/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L777JIBIWJV34HS7LXPIDWASG7TT4LNI/https://security.gentoo.org/glsa/202209-09https://www.debian.org/security/2022/dsa-5151