First published: Sun Jan 24 2021(Updated: )
Smarty before 3.1.39 allows code injection via an unexpected function name after a {function name= substring.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/smarty/smarty | <=3.1.38 | |
debian/smarty3 | 3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u1 3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u2 3.1.39-2+deb11u1 3.1.47-2 3.1.48-1 | |
composer/smarty/smarty | <3.1.39 | 3.1.39 |
Smarty | <3.1.39 | |
Debian | =9.0 | |
Debian | =10.0 | |
Debian | =11.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-26120 has a medium severity rating due to its potential for code injection via malicious function names in Smarty templates.
To fix CVE-2021-26120, upgrade Smarty to version 3.1.39 or later.
CVE-2021-26120 is caused by an insufficiently validated function name in Smarty templates that allows for code injection.
Smarty versions prior to 3.1.39 are affected by CVE-2021-26120.
Mitigating CVE-2021-26120 without upgrading is challenging; it is recommended to implement strict validation of user inputs in templates.