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

> Remote attackers can execute arbitrary scripts in other users' browsers via XSS in MyHelpDesk ticket creation and editing features.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** No
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-583g-5332-v4w5

## What is CVE-2002-0931?

CVE-2002-0931 is a high-severity cross-site scripting vulnerability in n/a, published on 31 Aug 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 vulnerabilities in MyHelpDesk 20020509, and possibly other versions, allows remote attackers to execute script as other users via a (1) Title or (2) Description when a new ticket is created by a support assistant, via the "id" parameter to the index.php script with the (3) tickettime, (4) ticketfiles, or (5) updateticketlog operations, or (6) via the update section when a ticket is edited.

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

It affects 1 product.


Products: Luis Bernardo Myhelpdesk.

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

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

## Is CVE-2002-0931 being exploited?

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

Public exploit code:

- MyHelpDesk 20020509 - HTML Injection (exploitdb)
- MyHelpDesk 20020509 - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0932](https://insights.sbomify.com/CVE-2002-0932/): SQL injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0931 is a high-severity cross-site scripting vulnerability in n/a, published on 31 Aug 2002. Any signed-in user can exploit it over the network, 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-0931 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-0931/ (Markdown: https://insights.sbomify.com/CVE-2002-0931/index.md)
```

## Sources

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

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