# CVE-2008-1066: Code injection in n/a

> Attackers can execute arbitrary PHP code via crafted templates in the Smarty library due to improper handling of null characters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1520-1, GHSA-v4j9-rxfp-35qc

## What is CVE-2008-1066?

CVE-2008-1066 is a high-severity code injection vulnerability in n/a, published on 28 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The modifier.regex_replace.php plugin in Smarty before 2.6.19, as used by Serendipity (S9Y) and other products, allows attackers to call arbitrary PHP functions via templates, related to a '\0' character in a search string.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-1066?

It affects 1 product.


Products: Smarty Smarty.

## How do I fix CVE-2008-1066?

Upgrade to a fixed version.

## Is CVE-2008-1066 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-5052](https://insights.sbomify.com/CVE-2009-5052/): Other in n/a (critical 10.0)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1066 and fix it if it is affected.

What it is: CVE-2008-1066 is a high-severity code injection vulnerability in n/a, published on 28 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1066 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-2008-1066/ (Markdown: https://insights.sbomify.com/CVE-2008-1066/index.md)
```

## Sources

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

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