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

> Remote attackers can execute arbitrary SQL commands via multiple parameters, potentially reading or modifying database contents.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 4 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v489-r8f5-qhp8

## What is CVE-2006-6270?

CVE-2006-6270 is a critical SQL injection vulnerability in n/a, published on 4 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in ASPMForum allow remote attackers to execute arbitrary SQL commands via (1) the soruid parameter in forum2.asp, (2) the ak parameter in kullanicilistesi.asp, (3) the kelimeler parameter in aramayap.asp, and (4) the kullaniciadi parameter in giris.asp; and allow remote authenticated users to execute arbitrary SQL commands via (5) the mesajno parameter in mesajkutum.asp.  NOTE: the harf parameter in kullanicilistesi.asp and the baslik parameter in forum.asp are already covered by CVE-2005-4141.

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

It affects 1 product.


Products: Kervancilar Aspmforum.

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

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

## Is CVE-2006-6270 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6270 is a critical SQL injection vulnerability in n/a, published on 4 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6270 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-2006-6270/ (Markdown: https://insights.sbomify.com/CVE-2006-6270/index.md)
```

## Sources

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

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