# CVE-2001-1100: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in the Compose Message page of W3Mail.

- **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:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cr38-99rq-q4pc

## What is CVE-2001-1100?

CVE-2001-1100 is a high-severity command injection vulnerability in n/a, published on 25 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

sendmessage.cgi in W3Mail 1.0.2, and possibly other CGI programs, allows remote attackers to execute arbitrary commands via shell metacharacters in any field of the 'Compose Message' page.

## Which versions are affected by CVE-2001-1100?

It affects 1 product.


Products: Spencer Miles W3mail.

## How do I fix CVE-2001-1100?

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

## Is CVE-2001-1100 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1100 and fix it if it is affected.

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

## Sources

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

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