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

> Remote attackers can execute arbitrary SQL commands via the key parameter in coupon_detail.asp, potentially accessing 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:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9ch8-g58r-59fj

## What is CVE-2006-6859?

CVE-2006-6859 is a critical SQL injection vulnerability in n/a, published on 4 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in coupon_detail.asp in Website Designs For Less Click N' Print Coupons 2005.01 and earlier allows remote attackers to execute arbitrary SQL commands via the key parameter.

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

It affects 1 product.


Products: Website Designs for Less Click N Print Coupons.

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

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

## Is CVE-2006-6859 being exploited?

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

Public exploit code:

- Click N Print Coupons 2006.01 - 'key' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6859 is a critical SQL injection vulnerability in n/a, published on 4 Jan 2007. 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-6859 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-6859/ (Markdown: https://insights.sbomify.com/CVE-2006-6859/index.md)
```

## Sources

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

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