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

> Remote attackers can inject scripts via mailbox parameters in SquirrelMail, requiring user interaction to execute malicious code.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Dec 2002
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-220, GHSA-m4rj-cp46-j9cp

## What is CVE-2002-1341?

CVE-2002-1341 is a medium-severity cross-site scripting vulnerability in Squirrelmail Squirrelmail, published on 11 Dec 2002. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in read_body.php for SquirrelMail 1.2.10, 1.2.9, and earlier allows remote attackers to insert script and HTML via the (1) mailbox and (2) passed_id parameters.

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

It affects 1 product.


Products: Squirrelmail Squirrelmail.

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

Upgrade to a fixed version.

## Is CVE-2002-1341 being exploited?

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

## Other vulnerabilities in Squirrelmail Squirrelmail

- [CVE-2002-0516](https://insights.sbomify.com/CVE-2002-0516/): Command injection in n/a (critical 10.0)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1341 is a medium-severity cross-site scripting vulnerability in Squirrelmail Squirrelmail, published on 11 Dec 2002. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-1341 in the wild and no public exploit code.

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

## Sources

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

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