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

> Remote authenticated administrators can execute arbitrary code via shell metacharacters in the kill parameter of ws_mail.cgi.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5jxq-vjr3-45cr

## What is CVE-2001-1343?

CVE-2001-1343 is a high-severity command injection vulnerability in n/a, published on 3 May 2002. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ws_mail.cgi in WebStore 400/400CS 4.14 allows remote authenticated WebStore administrators to execute arbitrary code via shell metacharacters in the kill parameter.

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

It affects 2 products.


Products: Cgicentral Webstore 400, Cgicentral Webstore 400cs.

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

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

## Is CVE-2001-1343 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1343 exists.

Public exploit code:

- cgiCentral WebStore 400 - Arbitrary Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-1344](https://insights.sbomify.com/CVE-2001-1344/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1343 is a high-severity command injection vulnerability in n/a, published on 3 May 2002. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1343 exists.

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-1343/ (Markdown: https://insights.sbomify.com/CVE-2001-1343/index.md)
```

## Sources

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

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