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

> Remote attackers can inject arbitrary scripts or HTML via user name and comment fields in MyGuestbook, requiring victim interaction to execute.

- **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:** No
- **Published:** 26 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p875-45x7-v8cm

## What is CVE-2002-0732?

CVE-2002-0732 is a high-severity cross-site scripting vulnerability in n/a, published on 26 Jul 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 vulnerability in MyGuestbook 1.0 allows remote attackers to execute arbitrary script or inject HTML via fields such as (1) user name or (2) comments.

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

It affects 1 product.


Products: Levcgi.com Myguestbook.

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

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

## Is CVE-2002-0732 being exploited?

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

Public exploit code:

- MyGuestbook 1.0 - Script Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2162](https://insights.sbomify.com/CVE-2005-2162/): Code injection in n/a (medium 5.0)
- [CVE-2003-1241](https://insights.sbomify.com/CVE-2003-1241/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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