# CVE-2024-35226: PHP Code Injection by malicious attribute in extends-tag in Smarty

> Malicious template authors can inject PHP code via the extends-tag, allowing remote code execution on applications using the Smarty library.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 May 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-35226, DSA-5830-1, GHSA-4rmg-292m-wg3w, UBUNTU-CVE-2024-35226, USN-7377-1

## What is CVE-2024-35226?

CVE-2024-35226 is a high-severity code injection vulnerability in smarty-php smarty, published on 28 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-35226?

4 open source packages ship an affected version, including smarty/smarty.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `smarty/smarty` | Packagist | From 3.0.0 | 4.5.3 |
| `smarty/smarty` | Packagist | From 3.0.0 | 4.5.3 |
| `smarty/smarty` | Packagist | From 5.0.0 | 5.1.1 |
| `smarty/smarty` | Packagist | From 5.0.0 | 5.1.1 |

## How do I fix CVE-2024-35226?

Upgrade smarty/smarty to a fixed version for your release line: 4.5.3 or 5.1.1.

## Is CVE-2024-35226 being exploited?

There is no known exploitation of CVE-2024-35226 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35226 and fix it if it is affected.

What it is: CVE-2024-35226 is a high-severity code injection vulnerability in smarty-php smarty, published on 28 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-35226 in the wild and no public exploit code.

Affected packages and fixed versions:
- smarty/smarty (Packagist): affected from 3.0.0; fixed in 4.5.3
- smarty/smarty (Packagist): affected from 3.0.0; fixed in 4.5.3
- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.1.1
- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-35226/ (Markdown: https://insights.sbomify.com/CVE-2024-35226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35226
- OSV: https://osv.dev/vulnerability/CVE-2024-35226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35226/
Summaries are generated and may contain mistakes; the official description above is the record.