# CVE-2002-0388: Cross-site scripting in n/a

> Remote attackers can execute arbitrary scripts via cross-site scripting in Mailman admin pages or Pipermail summaries.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v3cv-7ww7-7g63

## What is CVE-2002-0388?

CVE-2002-0388 is a high-severity cross-site scripting vulnerability in n/a, published on 31 May 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerabilities in Mailman before 2.0.11 allow remote attackers to execute script via (1) the admin login page, or (2) the Pipermail index summaries.

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

It affects 1 product.


Products: Gnu Mailman.

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

Upgrade to a fixed version.

## Is CVE-2002-0388 being exploited?

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

Public exploit code:

- GNU Mailman 2.0.x - Admin Login Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-6893](https://insights.sbomify.com/CVE-2016-6893/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-7123](https://insights.sbomify.com/CVE-2016-7123/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2005-4153](https://insights.sbomify.com/CVE-2005-4153/): Denial of service in n/a (high 7.8)
- [CVE-2006-2191](https://insights.sbomify.com/CVE-2006-2191/): Other in n/a (high 7.5)
- [CVE-2004-1143](https://insights.sbomify.com/CVE-2004-1143/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0388 is a high-severity cross-site scripting vulnerability in n/a, published on 31 May 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0388 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-2002-0388/ (Markdown: https://insights.sbomify.com/CVE-2002-0388/index.md)
```

## Sources

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

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