# CVE-2006-6050: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via vulnerable parameters in the Texas Rank'em web application.

- **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:** 22 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ccww-c84c-mm5c

## What is CVE-2006-6050?

CVE-2006-6050 is a high-severity SQL injection vulnerability in n/a, published on 22 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in ClickTech Texas Rank'em allow remote attackers to execute arbitrary SQL commands via the (1) selPlayer parameter to player.asp or the (2) tournament_id parameter to tournaments.asp.

## Which versions are affected by CVE-2006-6050?

It affects 1 product.


Products: Clicktech Texas Rankem.

## How do I fix CVE-2006-6050?

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

## Is CVE-2006-6050 being exploited?

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

Public exploit code:

- Texas Rankem - 'selPlayer' SQL Injection (exploitdb)
- Texas Rankem - 'tournament_id' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6050 and fix it if it is affected.

What it is: CVE-2006-6050 is a high-severity SQL injection vulnerability in n/a, published on 22 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6050 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-2006-6050/ (Markdown: https://insights.sbomify.com/CVE-2006-6050/index.md)
```

## Sources

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

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