Approved changes feed: RSS · Atom
cpe:2.3:a:smarty-php:smarty:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Smarty Php (30d091b1-ae43-5dec-ae65-96792c415b9a) |
|---|---|
| Product | Smarty (b9412e0c-ef84-587f-a7d0-5948e5e04bc2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-62992 |
vulnerable | 2026-09-16 04:32:53.205486 |
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.
Published: 2026-08-07T15:02:28.873Z
Updated: 2026-08-07T16:00:28.634Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-62996 |
vulnerable | 2026-09-16 04:32:53.130446 |
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.
Published: 2026-08-07T15:04:52.662Z
Updated: 2026-08-07T17:08:09.710Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-35226 |
vulnerable | 2026-06-08 06:37:35.479232 |
PHP Code Injection by malicious attribute in extends-tag in Smarty
HIGH (7.3)
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.
Published: 2024-05-28T20:55:00.884Z
Updated: 2025-11-03T21:54:58.981Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-28447 |
vulnerable | 2026-06-08 06:01:10.895708 |
Cross site scripting vulnerability in Javascript escaping in smarty/smarty
HIGH (7.1)
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.
Published: 2023-03-28T20:07:39.103Z
Updated: 2025-11-03T21:47:36.097Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-29221 |
vulnerable | 2026-06-08 05:42:47.365407 |
PHP Code Injection by malicious block or filename in Smarty
HIGH (8.8)
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.
Published: 2022-05-24T00:00:00.000Z
Updated: 2025-04-23T18:22:54.999Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-29454 |
vulnerable | 2026-06-08 05:31:26.392918 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21408 |
vulnerable | 2026-06-08 05:29:11.960259 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.