# CVE-2009-5052: Other in n/a

> Multiple unspecified vulnerabilities in the Smarty PHP template engine allow attackers to potentially compromise applications using this library.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 3 Feb 2011
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2009-5052, GHSA-v7g6-6mrr-692g

## What is CVE-2009-5052?

CVE-2009-5052 is a critical vulnerability in n/a, published on 3 Feb 2011. 

### Official description

Multiple unspecified vulnerabilities in Smarty before 3.0.0 beta 6 have unknown impact and attack vectors.

## Which versions are affected by CVE-2009-5052?

It affects 1 product.


Products: Smarty Smarty.

## How do I fix CVE-2009-5052?

Upgrade to a fixed version.

## Is CVE-2009-5052 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4722](https://insights.sbomify.com/CVE-2010-4722/): Other in n/a (critical 10.0)
- [CVE-2010-4724](https://insights.sbomify.com/CVE-2010-4724/): Other in n/a (critical 10.0)
- [CVE-2010-4725](https://insights.sbomify.com/CVE-2010-4725/): Code injection in n/a (critical 10.0)
- [CVE-2010-4726](https://insights.sbomify.com/CVE-2010-4726/): Other in n/a (critical 10.0)
- [CVE-2010-4727](https://insights.sbomify.com/CVE-2010-4727/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5052 and fix it if it is affected.

What it is: CVE-2009-5052 is a critical vulnerability in n/a, published on 3 Feb 2011. 
Exploitation: There is no known exploitation of CVE-2009-5052 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2009-5052/ (Markdown: https://insights.sbomify.com/CVE-2009-5052/index.md)
```

## Sources

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

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