# CVE-2000-0125: SQL injection in n/a

> Remote attackers can exploit SQL injection in wwwthreads forums to gain elevated privileges and access sensitive data.

- **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:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vmr6-rxwm-662f

## What is CVE-2000-0125?

CVE-2000-0125 is a high-severity SQL injection vulnerability in n/a, published on 8 Feb 2000. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wwwthreads does not properly cleanse numeric data or table names that are passed to SQL queries, which allows remote attackers to gain privileges for wwwthreads forums.

## Which versions are affected by CVE-2000-0125?

It affects 1 product.


Products: Wired Community Software Wwwthreads.

## How do I fix CVE-2000-0125?

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

## Is CVE-2000-0125 being exploited?

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

Public exploit code:

- Wired Community Software WWWThreads 5.0 - SQL Command Input (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-3909](https://insights.sbomify.com/CVE-2006-3909/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-1958](https://insights.sbomify.com/CVE-2006-1958/): SQL injection in n/a (medium 6.4)
- [CVE-2006-5059](https://insights.sbomify.com/CVE-2006-5059/): Cross-site scripting in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0125 and fix it if it is affected.

What it is: CVE-2000-0125 is a high-severity SQL injection vulnerability in n/a, published on 8 Feb 2000. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0125 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-2000-0125/ (Markdown: https://insights.sbomify.com/CVE-2000-0125/index.md)
```

## Sources

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

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