# CVE-2005-2221: SQL injection in n/a

> Remote attackers can inject SQL commands into Dragonfly Commerce via multiple parameters, potentially reading or modifying database contents.

- **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:** 12 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wfvx-mj68-xg56

## What is CVE-2005-2221?

CVE-2005-2221 is a high-severity SQL injection vulnerability in n/a, published on 12 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Dragonfly Commerce allows remote attackers to modify SQL statements and possibly execute arbitrary SQL commands via the (1) key parameter to dc_Categoriesview.asp, (2) dc_productslist_Clearance.asp, (3) PID parameter to ratings.asp, (4) dc_Productsview.asp, (5) start, (6) key_mp, (7) searchtype, or (8) psearch parameters to dc_forum_Postslist.asp.  NOTE: the vendor has disputed this issue, saying that the error messages arise from invalid category and product numbers.  Assuming that this is the case, the issue still satisfies the CVE definition of "exposure.

## Which versions are affected by CVE-2005-2221?

It affects 1 product.


Products: Incredible Interactive Dragonfly Commerce.

## How do I fix CVE-2005-2221?

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

## Is CVE-2005-2221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2220](https://insights.sbomify.com/CVE-2005-2220/): Business logic in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2221 and fix it if it is affected.

What it is: CVE-2005-2221 is a high-severity SQL injection vulnerability in n/a, published on 12 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2221 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-2005-2221/ (Markdown: https://insights.sbomify.com/CVE-2005-2221/index.md)
```

## Sources

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

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