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

> Remote attackers can execute arbitrary commands via a backdoor in the Etomite CMS manager interface.

- **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:** No
- **Published:** 20 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xrx4-hm38-w6hm

## What is CVE-2006-0325?

CVE-2006-0325 is a high-severity command injection vulnerability in n/a, published on 20 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Etomite Content Management System 0.6, and possibly earlier versions, when downloaded from the web site in January 2006 after January 10, contains a back door in manager/includes/todo.inc.php, which allows remote attackers to execute arbitrary commands via the "cij" parameter.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Etomite Etomite.

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

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

## Is CVE-2006-0325 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-7070](https://insights.sbomify.com/CVE-2006-7070/): File upload in n/a (high 7.5)
- [CVE-2006-5242](https://insights.sbomify.com/CVE-2006-5242/): SQL injection in n/a (high 7.5)
- [CVE-2006-6048](https://insights.sbomify.com/CVE-2006-6048/): SQL injection in n/a (medium 6.8)
- [CVE-2006-3904](https://insights.sbomify.com/CVE-2006-3904/): SQL injection in n/a (medium 6.8)
- [CVE-2006-6047](https://insights.sbomify.com/CVE-2006-6047/): Path traversal in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0325 is a high-severity command injection vulnerability in n/a, published on 20 Jan 2006. 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-2006-0325 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-0325/ (Markdown: https://insights.sbomify.com/CVE-2006-0325/index.md)
```

## Sources

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

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