# CVE-2006-0845: Command injection in n/a

> Administrative users can execute arbitrary commands by configuring a malicious sendmail path in Leif Wright's Blog.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fhj8-953f-fx7h

## What is CVE-2006-0845?

CVE-2006-0845 is a medium-severity command injection vulnerability in n/a, published on 22 Feb 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Leif M. Wright's Blog 3.5 allows remote authenticated users with administrative privileges to execute arbitrary programs, including shell commands, by configuring the sendmail path to a malicious pathname.

## Which versions are affected by CVE-2006-0845?

It affects 1 product.


Products: Leif M. Wright Web Blog.

## How do I fix CVE-2006-0845?

No fix has been published for CVE-2006-0845 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-0845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0844](https://insights.sbomify.com/CVE-2006-0844/): Auth bypass in n/a (high 7.5)
- [CVE-2004-2347](https://insights.sbomify.com/CVE-2004-2347/): Command injection in n/a (high 7.5)
- [CVE-2006-0843](https://insights.sbomify.com/CVE-2006-0843/): Information disclosure in n/a (medium 5.0)
- [CVE-2004-2127](https://insights.sbomify.com/CVE-2004-2127/): Path traversal in n/a (medium 5.0)
- [CVE-2006-0846](https://insights.sbomify.com/CVE-2006-0846/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0845 and fix it if it is affected.

What it is: CVE-2006-0845 is a medium-severity command injection vulnerability in n/a, published on 22 Feb 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0845 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-2006-0845/ (Markdown: https://insights.sbomify.com/CVE-2006-0845/index.md)
```

## Sources

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

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