# CVE-2005-2220: Business logic in n/a

> Remote attackers can manipulate product prices by modifying hidden form fields in Dragonfly Commerce, leading to unauthorized price changes.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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-jrhm-wvch-w2v8

## What is CVE-2005-2220?

CVE-2005-2220 is a medium-severity 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

Dragonfly Commerce allows remote attackers to change a product price by modifying the x_DragonflyCartProductPrice hidden field to (1) dc_Categorieslist.asp, (2) dc_Categoriesview.asp, (3) dc_productslist.asp, and (4) dc_productslist_Clearance.asp.  NOTE: the vendor has disputed this issue, saying that "Dragonfly Commerce does not allow for editing prices nor does it allow for viewing information about clients stored in the database except by the store owner and authorized staff as appointed in the store administration."  However, SecurityTracker claims that they have been able to confirm the problem

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

It affects 1 product.


Products: Incredible Interactive Dragonfly Commerce.

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

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

## Is CVE-2005-2220 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2221](https://insights.sbomify.com/CVE-2005-2221/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2220 is a medium-severity 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-2220 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-2220/ (Markdown: https://insights.sbomify.com/CVE-2005-2220/index.md)
```

## Sources

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

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