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

> Remote attackers can execute arbitrary scripts in other users' browsers via malicious IMG tags in Snitz Forums.

- **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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-qp87-xr37-3cmm

## What is CVE-2002-0329?

CVE-2002-0329 is a high-severity cross-site scripting vulnerability in n/a, published on 2 Apr 2003. 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 vulnerability in Snitz Forums 2000 3.3.03 and earlier allows remote attackers to execute arbitrary script as other Forums 2000 users via Javascript in an IMG tag.

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

It affects 1 product.


Products: Snitz Communications Snitz Forums 2000.

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

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

## Is CVE-2002-0329 being exploited?

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

Public exploit code:

- Snitz Forums 2000 3.0/3.1/3.3 - Image Tag Cross-Agent Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0493](https://insights.sbomify.com/CVE-2003-0493/): Auth bypass in n/a (critical 10.0)
- [CVE-2003-0494](https://insights.sbomify.com/CVE-2003-0494/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-5603](https://insights.sbomify.com/CVE-2006-5603/): SQL injection in n/a (critical 9.8)
- [CVE-2012-5313](https://insights.sbomify.com/CVE-2012-5313/): SQL injection in n/a (high 7.5)
- [CVE-2010-4826](https://insights.sbomify.com/CVE-2010-4826/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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