Template authors could inject php code by choosing a malicous {block} name or {include} file name. Sites that cannot fully trust template authors should update asap.
Please upgrade to the most recent version of Smarty v3 or v4.
Is there a way for users to fix or remediate the vulnerability without upgrading?
Are there any links users can visit to find out more?
If you have any questions or comments about this advisory:
* Open an issue in the Smarty repo
| Score | Percentile |
|---|---|
| 25.50% | 96.23% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 8.8 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-634x-pc3q-cf4c ↗ |
| CVE | CVE-2022-29221 ↗ |
| CWE id | Name |
|---|---|
| CWE-94 | Improper Control of Generation of Code ('Code Injection') |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| composer | smarty/smarty | < 3.1.45 | 3.1.45 | — |
| composer | smarty/smarty | >= 4.0.0, < 4.1.1 | 4.1.1 | — |