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

> Remote attackers can execute arbitrary SQL commands via parameters in GA Forum Light, though the vendor disputes the vulnerability's existence.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6634-4hvh-mmj4

## What is CVE-2006-0669?

CVE-2006-0669 is a high-severity SQL injection vulnerability in n/a, published on 13 Feb 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in archive.asp in GA's Forum Light allow remote attackers to execute arbitrary SQL commands via the (1) Forum and (2) pages parameter.  NOTE: SecurityTracker says that the vendor has disputed this issue, saying that GA Forum Light does not use an SQL database.  SecurityTracker's research indicates that the original problem could be due to a vbscript parsing error based on invalid arguments

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

It affects 1 product.


Products: Gasoft Gas Forum Light.

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

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

## Is CVE-2006-0669 being exploited?

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

Public exploit code:

- GA's Forum Light - 'Archive.asp' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0669 is a high-severity SQL injection vulnerability in n/a, published on 13 Feb 2006. It can be exploited 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-2006-0669 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-0669/ (Markdown: https://insights.sbomify.com/CVE-2006-0669/index.md)
```

## Sources

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

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