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

> Remote attackers can execute arbitrary SQL commands via the iType parameter in type.asp across multiple DUware products.

- **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:** 3 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8cpm-2q4p-34xp

## What is CVE-2005-3976?

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

### Official description

SQL injection vulnerability in type.asp, as used in multiple DUware products including (1) DUamazon 3.1, (2) DUarticle 1.1, (3) DUclassified 4.2, (4) DUdirectory 3.1 and DUdirectory Pro 3.0 and 3.0 SQL, (5) DUdownload 1.1, (6) DUgallery 3.3, (7) DUnews 1.1, and (8) DUpaypal 3.1 and DUpaypal Pro 3.0, allows remote attackers to execute arbitrary SQL commands via the iType parameter.

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

It affects 11 products.


Products: Duware Duamazon, Duware Duarticle, Duware Duclassified, Duware Dudirectory, Duware Dudirectory Pro, Duware Dudirectory Pro Sql, Duware Dudownload, Duware Dugallery, Duware Dunews, Duware Dupaypal, Duware Dupaypal Pro.

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

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

## Is CVE-2005-3976 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3976 is a high-severity SQL injection vulnerability in n/a, published on 3 Dec 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-3976 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-3976/ (Markdown: https://insights.sbomify.com/CVE-2005-3976/index.md)
```

## Sources

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

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