Skip to content

Product

ubuntu/smarty3 vulnerabilities

16 published CVES affecting ubuntu/smarty3, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
16
Critical
3
High
7
Medium
6
Low
0
Unscored
0
CISA KEV
0

Latest ubuntu/smarty3 CVEs

Newest publication first

  1. MediumCVSS 6.9 EPSS 0.57%

    Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 4.5.7 and 5.8.2, depending on the release line, Smarty's {fetch} handling in libs/plugins/function.fetch.php and src/FunctionHandler/Fetch.php used Securit...

  2. MediumCVSS 6.9 EPSS 0.51%

    Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a te...

  3. MediumCVSS 6.9 EPSS 0.53%

    Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 5.8.2 (and 4.5.7 on the 4.x line), Security::_checkDir() does not fully resolve symbolic links before validating that a requested path lies within a config...

  4. HighCVSS 8.8 EPSS 4.9% PoC

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

  5. HighCVSS 8.8 EPSS 1.9% PoC

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

  6. HighCVSS 7.5 EPSS 3.5% PoC

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

  7. CriticalCVSS 9.8 EPSS 3.1%

    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.

  8. HighCVSS 7.5 EPSS 3.1%

    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.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.