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

> Remote attackers can execute arbitrary scripts and steal cookies from other users via post titles or bodies in IcrediBB.

- **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:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f2c8-j2m9-4qrx

## What is CVE-2002-0590?

CVE-2002-0590 is a high-severity cross-site scripting vulnerability in n/a, published on 11 Jun 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 (CSS) vulnerability in IcrediBB 1.1 Beta allows remote attackers to execute arbitrary script and steal cookies as other IcrediBB users via the (1) title or (2) body of posts.

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

It affects 1 product.


Products: Icredibb Icredibb.

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

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

## Is CVE-2002-0590 being exploited?

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

Public exploit code:

- IcrediBB 1.1 - Script Injection (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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