p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in smarty/smarty

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für smarty/smarty: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 18

  1. CVE-2026-62993

    Mittel · CVSS 6.9EPSS 0,57%Korrektur verfügbar

    Smarty: SSRF via redirect bypass of trusted_uri using {fetch}

    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 Security::isTrustedUri() to validate only the initial remote URL against trusted_uri when a security policy was active. For resources handled by file_get_contents(), including HTTPS URLs, PHP followed HTTP redirects by default. An attacker who could supply or influence a fetch target and had an open redirect on a trusted host could redirect the request to an attacker-chosen

    • Auf 4.5.7 aktualisieren
    • Auf 5.8.2 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-62996

    Mittel · CVSS 6.9EPSS 0,51%Korrektur verfügbar

    Smarty Security stream restriction bypass through stream: resource

    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 template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.

    • Auf 5.8.4 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-62992

    Mittel · CVSS 6.9EPSS 0,53%Korrektur verfügbar

    Smarty: Symlink path traversal out of trusted directories

    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 configured secure directory. An attacker able to place or reference a symlink within a directory Smarty treats as trusted (e.g., a template or config directory) could use it to point outside the intended secure directory, bypassing the containment check and reading arbitrary files accessible to the PHP process. This issue is fixed in versions 5.8.2 and 4.5.7.

    • Auf 4.5.7 aktualisieren
    • Auf 5.8.2 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-35226

    Hoch · CVSS 7.3EPSS 0,51%Korrektur verfügbar

    PHP Code Injection by malicious attribute in extends-tag in Smarty

    Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. In affected versions template authors could inject php code by choosing a malicious file name for an extends-tag. Sites that cannot fully trust template authors should update asap. All users are advised to update. There is no patch for users on the v3 branch. There are no known workarounds for this vulnerability.

    • Auf 4.5.3 aktualisieren
    • Auf 5.1.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-28447

    Hoch · CVSS 7.1EPSS 1,02%Korrektur verfügbar

    Cross site scripting vulnerability in Javascript escaping in smarty/smarty

    Smarty is a template engine for PHP. In affected versions smarty did not properly escape javascript code. 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. Users are advised to upgrade to either version 3.1.48 or to 4.3.1 to resolve this issue. There are no known workarounds for this vulnerability.

    • Auf 3.1.48 aktualisieren
    • Auf 4.3.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2018-25047

    Mittel · CVSS 5.4EPSS 1,1%Korrektur verfügbar

    CVE-2018-25047

    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.

    • Auf 3.1.47 aktualisieren
    • Auf 4.2.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2022-29221

    Hoch · CVSS 8.8EPSS 4,91%Korrektur verfügbar

    PHP Code Injection by malicious block or filename in Smarty

    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.

    • Auf 3.1.45 aktualisieren
    • Auf 4.1.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2021-29454

    Hoch · CVSS 8.1EPSS 1,8%Korrektur verfügbar

    Sandbox Escape by math function in smarty

    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 provided data to the math function, external users could run arbitrary PHP code by crafting a malicious math string. Users should upgrade to version 3.1.42 or 4.0.2 to receive a patch.

    • Auf 3.1.42 aktualisieren
    • Auf 4.0.2 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2021-21408

    Hoch · CVSS 8.8EPSS 2,08%Korrektur verfügbar

    Access to restricted PHP code by dynamic static class access in smarty

    Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to versions 3.1.43 and 4.0.3, template authors could run restricted static php methods. Users should upgrade to version 3.1.43 or 4.0.3 to receive a patch.

    • Auf 3.1.43 aktualisieren
    • Auf 4.0.3 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2018-13982

    Hoch · CVSS 7.5EPSS 3,46%Korrektur verfügbar

    CVE-2018-13982

    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.

    • Auf 3.1.33 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2018-16831

    Mittel · CVSS 5.9EPSS 2,66%Korrektur verfügbar

    CVE-2018-16831

    Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:./../ substring in an include statement.

    • Auf 3.1.33 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2012-4437

    Nicht bewertetEPSS 2,46%Korrektur verfügbar

    CVE-2012-4437

    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.

    • Auf 3.1.12 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2009-5054

    Nicht bewertetEPSS 1,59%Korrektur verfügbar

    CVE-2009-5054

    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.

    • Auf 3.0.0-beta4 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →