Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,049
Published in 7 days
1,605
Critical in 30 days
482
Actively exploited
542
Clear filters

Results for “Smarty”

37 vulnerabilities
  1. Critical 9.2

    CVE-2026-82531 · Smarty

    Missing nocache-hash restoration lets assigned data inject executable PHP into regenerated cache files

    Published 4 Oct 2026 · Fixed in 4.5.8, 5.8.5 · CVE Program, Project advisories (GitHub)
  2. Medium

    CVE-2026-62996 · Smarty

    Smarty Security stream restriction bypass through stream: resource

    Published 20 Jul 2026 · Fixed in 5.8.4 · Project advisories (GitHub)
  3. Medium

    CVE-2026-62993 · Smarty

    SSRF via redirect bypass of trusted_uri using {fetch}

    Published 20 Jul 2026 · Fixed in 4.5.7, 5.8.2 · Project advisories (GitHub)
  4. Medium

    CVE-2026-62992 · Smarty

    Symlink path traversal out of trusted directories

    Published 20 Jul 2026 · Fixed in 4.5.7, 5.8.2 · Project advisories (GitHub)
  5. High

    CVE-2024-35226 · Smarty

    PHP Code Injection by malicious attribute in extends-tag

    Published 28 May 2024 · Fixed in 4.5.3, 5.2.0 · Project advisories (GitHub)
  6. Medium 4.8

    CVE-2023-41661 · Smarty

    Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in PressPage Entertainment Inc. Smarty for WordPress plugin <= 3.1.35 versions.

    Published 29 Sept 2023 · NVD
  7. Medium 6.1

    CVE-2023-28447 · Smarty

    Cross site scripting vulnerability in Javascript escaping

    Published 28 Mar 2023 · Fixed in 3.1.48, 4.3.1 · NVD, Project advisories (GitHub)
  8. Medium 5.4

    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 could be parameterized using GET or POST input parameters, could allow injection of JavaScript code by a user.

    Published 15 Sept 2022 · Fixed in 3.1.47, 4.2.1 · NVD
  9. High 8.8

    CVE-2022-29221 · Smarty

    PHP Code Injection by malicious block or filename

    Published 17 May 2022 · Fixed in 3.1.45, 4.1.1 · NVD, Project advisories (GitHub)
  10. High 8.8

    CVE-2021-21408 · Smarty

    Access to restricted PHP code by dynamic static class access

    Published 10 Jan 2022 · Fixed in 3.1.43, 4.0.3 · NVD, Project advisories (GitHub)
  11. High 8.8

    CVE-2021-29454 · Smarty

    Sandbox Escape by math function

    Published 9 Jan 2022 · Fixed in 3.1.42, 4.0.2 · NVD, Project advisories (GitHub)
  12. High 7.5

    CVE-2021-26119 · Smarty

    Sandbox escape through template_object

    Published 21 Feb 2021 · Fixed in 3.1.39 · NVD, Project advisories (GitHub)
  13. Critical 9.8

    CVE-2021-26120 · Smarty

    PHP Code Injection by malicious function name

    Published 21 Feb 2021 · Fixed in 3.1.39 · NVD, Project advisories (GitHub)
  14. High 8.8

    CVE-2020-35625 · MediaWiki

    An issue was discovered in the Widgets extension for MediaWiki through 1.35.1. Any user with the ability to edit pages within the Widgets namespace could call any static function within any class (defined within PHP or MediaWiki) via a crafted HTML comment, related to a Smarty template. For example, a person in the Widget Editors group could use \MediaWiki\Shell\Shell::command within a comment.

    Published 21 Dec 2020 · NVD
  15. Critical 9.8

    CVE-2011-1028 · Smarty

    The $smarty.template variable in Smarty3 allows attackers to possibly execute arbitrary PHP code via the sysplugins/smarty_internal_compile_private_special_variable.php file.

    Published 20 Nov 2019 · Fixed in 3.0.7 · NVD
  16. High 7.5

    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 sanitization. This allows attackers controlling the executed template code to bypass the trusted directory security restriction and read arbitrary files.

    Published 18 Sept 2018 · Fixed in 3.1.33 · NVD
  17. Medium 5.9

    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.

    Published 11 Sept 2018 · NVD
  18. Critical 9.8

    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 template name.

    Published 3 Jan 2018 · Fixed in 3.1.32 · NVD
  19. High 7.5

    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 "{literal}<{/literal}script language=php>" in a template.

    Published 3 Nov 2014 · NVD
  20. Medium 4.3

    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 arbitrary web script or HTML via unspecified vectors that trigger a Smarty exception.

    Published 1 Oct 2012 · NVD
  21. Medium 4.3

    CVE-2012-4277 · Smarty

    Cross-site scripting (XSS) vulnerability in the smarty_function_html_options_optoutput function in distribution/libs/plugins/function.html_options.php in Smarty before 3.1.8 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    Published 13 Aug 2012 · NVD
  22. High 10.0

    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.

    Published 3 Feb 2011 · NVD
  23. High 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 CVE-2009-1669.

    Published 3 Feb 2011 · NVD
  24. High 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 attack vectors.

    Published 3 Feb 2011 · NVD
  25. High 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.

    Published 3 Feb 2011 · NVD
  26. High 9.3

    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, which has unspecified impact and remote attack vectors.

    Published 3 Feb 2011 · NVD
  27. High 10.0

    CVE-2010-4722 · Smarty

    Unspecified vulnerability in the fetch plugin in Smarty before 3.0.2 has unknown impact and remote attack vectors.

    Published 3 Feb 2011 · NVD
  28. High 7.5

    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 access restrictions via standard filesystem operations.

    Published 3 Feb 2011 · NVD
  29. High 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 file.

    Published 3 Feb 2011 · NVD
  30. High 10.0

    CVE-2009-5052 · Smarty

    Multiple unspecified vulnerabilities in Smarty before 3.0.0 beta 6 have unknown impact and attack vectors.

    Published 3 Feb 2011 · NVD
  31. High 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 commands via shell metacharacters in the equation attribute of the math function. NOTE: some of these details are obtained from third party information.

    Published 18 May 2009 · NVD
  32. High 7.5

    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 PHP code via vectors related to templates and a \ (backslash) before a dollar-sign character.

    Published 31 Oct 2008 · NVD
  33. High 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 code via vectors related to templates and (1) a dollar-sign character, aka "php executed in templates;" and (2) a double quoted literal string, aka a "function injection security hole." NOTE: each vector affects slightly different SVN revisions.

    Published 31 Oct 2008 · NVD
  34. High 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 PHP functions via templates, related to a '\0' character in a search string.

    Published 28 Feb 2008 · NVD
  35. High 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 in the SMARTY_DIR parameter. NOTE: this issue is disputed by CVE and a third party because SMARTY_DIR is a constant

    Published 12 Apr 2007 · NVD
  36. Critical 9.8

    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 the filename parameter. NOTE: in the original disclosure, filename is used in a function definition, so this report is probably incorrect

    Published 3 Mar 2007 · NVD
  37. High 7.5

    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 code.

    Published 2 May 2005 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.