# CVE-2002-0903: Business logic in n/a

> Remote attackers can hijack new user accounts by brute-forcing predictable registration codes and user IDs in WoltLab Burning Board.

- **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:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m6q2-xqp2-xxxv

## What is CVE-2002-0903?

CVE-2002-0903 is a high-severity vulnerability in n/a, published on 31 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

register.php for WoltLab Burning Board (wbboard) 1.1.1 uses a small number of random values for the "code" parameter that is provided to action.php to approve a new registration, along with predictable new user ID's, which allows remote attackers to hijack new user accounts via a brute force attack on the new user ID and the code value.

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

It affects 1 product.


Products: Woltlab Burning Board.

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

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

## Is CVE-2002-0903 being exploited?

There is no known exploitation of CVE-2002-0903 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-0857](https://insights.sbomify.com/CVE-2008-0857/): SQL injection in n/a (high 7.5)
- [CVE-2007-1518](https://insights.sbomify.com/CVE-2007-1518/): SQL injection in n/a (high 7.5)
- [CVE-2007-0388](https://insights.sbomify.com/CVE-2007-0388/): SQL injection in n/a (high 7.5)
- [CVE-2006-5029](https://insights.sbomify.com/CVE-2006-5029/): SQL injection in n/a (high 7.5)
- [CVE-2006-3254](https://insights.sbomify.com/CVE-2006-3254/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0903 is a high-severity vulnerability in n/a, published on 31 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0903 in the wild and no public exploit code.

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-0903/ (Markdown: https://insights.sbomify.com/CVE-2002-0903/index.md)
```

## Sources

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

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