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

> Remote attackers can inject scripts via email MIME headers, potentially executing code in the context of users viewing the archive.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1307, DSA-199, GHSA-4ghg-jxgx-f5gm

## What is CVE-2002-1307?

CVE-2002-1307 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Sep 2004. 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 vulnerability (XSS) in MHonArc 2.5.12 and earlier allows remote attackers to insert script or HTML via an email message with the script in a MIME header name.

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

It affects 1 product.


Products: Mhonarc Mhonarc.

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

Upgrade to a fixed version.

## Is CVE-2002-1307 being exploited?

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

Public exploit code:

- Mhonarc 2.5.x - Mail Header HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0738](https://insights.sbomify.com/CVE-2002-0738/): Cross-site scripting in n/a (high 7.5)
- [CVE-2010-1677](https://insights.sbomify.com/CVE-2010-1677/): Denial of service in n/a (medium 5.0)
- [CVE-2010-4524](https://insights.sbomify.com/CVE-2010-4524/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2002-1388](https://insights.sbomify.com/CVE-2002-1388/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1307 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Sep 2004. 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-1307 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-1307/ (Markdown: https://insights.sbomify.com/CVE-2002-1307/index.md)
```

## Sources

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

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