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

> Remote privileged attackers can execute arbitrary commands on the web server in WeBWorK, requiring an upgrade to mitigate.

- **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:** 27 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4wwc-5xpr-v7cw

## What is CVE-2006-0446?

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

### Official description

Unspecified vulnerability in WeBWorK 2.1.3 and 2.2-pre1 allows remote privileged attackers to execute arbitrary commands as the web server via unknown attack vectors.

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

It affects 1 product.


Products: Webwork Webwork.

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

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

## Is CVE-2006-0446 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2839](https://insights.sbomify.com/CVE-2006-2839/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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