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

> Remote attackers can execute arbitrary script and steal cookies via crafted IMG tags in YaBB bulletin board messages.

- **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:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cj73-32hf-pwxx

## What is CVE-2002-0117?

CVE-2002-0117 is a high-severity cross-site scripting vulnerability in n/a, published on 25 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 vulnerability in Yet Another Bulletin Board (YaBB) 1 Gold SP 1 and earlier allows remote attackers to execute arbitrary script and steal cookies via a message containing encoded Javascript in an IMG tag.

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

It affects 1 product.


Products: Yabb Yabb.

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

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

## Is CVE-2002-0117 being exploited?

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

Public exploit code:

- YaBB 9.1.2000 - Cross-Agent Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3208](https://insights.sbomify.com/CVE-2007-3208/): Other in n/a (critical 10.0)
- [CVE-2004-2403](https://insights.sbomify.com/CVE-2004-2403/): Cross-site request forgery in n/a (critical 10.0)
- [CVE-2004-0343](https://insights.sbomify.com/CVE-2004-0343/): SQL injection in n/a (critical 10.0)
- [CVE-2013-2057](https://insights.sbomify.com/CVE-2013-2057/): Path traversal in YaBB (critical 9.8)
- [CVE-2006-3275](https://insights.sbomify.com/CVE-2006-3275/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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