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

> Remote attackers can execute arbitrary SQL commands and disclose paths via vulnerable parameters in APT-webshop-system.

- **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:** 10 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jq2j-c7xr-7r39

## What is CVE-2006-1685?

CVE-2006-1685 is a high-severity SQL injection vulnerability in n/a, published on 10 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in modules.php in APT-webshop-system 4.0 PRO, 3.0 BASIC, and 3.0 LIGHT allow remote attackers to execute arbitrary SQL commands via the (1) group, (2) seite, and (3) id parameter, possibly involving the artikel functionality.  NOTE: this vulnerability also allows resultant path disclosure when the SQL queries are invalid.

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

It affects 1 product.


Products: Apt Apt-Webshop-System.

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

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

## Is CVE-2006-1685 being exploited?

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

Public exploit code:

- APT-webshop 3.0/4.0 - 'modules.php' Multiple SQL Injections (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1686](https://insights.sbomify.com/CVE-2006-1686/): Path traversal in n/a (medium 5.0)
- [CVE-2006-1687](https://insights.sbomify.com/CVE-2006-1687/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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