# CVE-2002-0516: Command injection in n/a

> Authenticated users can execute arbitrary commands by manipulating the THEME cookie variable in SquirrelMail.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3v4v-w999-cvf5

## What is CVE-2002-0516?

CVE-2002-0516 is a critical command injection vulnerability in Squirrelmail Squirrelmail, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SquirrelMail 1.2.5 and earlier allows authenticated SquirrelMail users to execute arbitrary commands by modifying the THEME variable in a cookie.

## Which versions are affected by CVE-2002-0516?

It affects 1 product.


Products: Squirrelmail Squirrelmail.

## How do I fix CVE-2002-0516?

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

## Is CVE-2002-0516 being exploited?

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

Public exploit code:

- SquirrelMail 1.2.x - Theme Remote Command Execution (exploitdb)

## Other vulnerabilities in Squirrelmail Squirrelmail

- [CVE-2020-14932](https://insights.sbomify.com/CVE-2020-14932/): Deserialization in n/a (critical 9.8)
- [CVE-2020-14933](https://insights.sbomify.com/CVE-2020-14933/): Deserialization in n/a (high 8.8)
- [CVE-2017-7692](https://insights.sbomify.com/CVE-2017-7692/): Command injection in n/a (high 8.8)
- [CVE-2007-2631](https://insights.sbomify.com/CVE-2007-2631/): Cross-site request forgery in n/a (high 7.5)
- [CVE-2006-2842](https://insights.sbomify.com/CVE-2006-2842/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0516 and fix it if it is affected.

What it is: CVE-2002-0516 is a critical command injection vulnerability in Squirrelmail Squirrelmail, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0516 exists.

Affected product: Squirrelmail Squirrelmail. 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-2002-0516/ (Markdown: https://insights.sbomify.com/CVE-2002-0516/index.md)
```

## Sources

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

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