# CVE-2006-0698: Other in n/a

> Unspecified vulnerabilities in Zen Cart allow remote attackers to cause unknown impacts via vectors other than SQL injection.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 15 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mmqr-h8r7-4rx7

## What is CVE-2006-0698?

CVE-2006-0698 is a critical vulnerability in n/a, published on 15 Feb 2006. It can be exploited over the network.

### Official description

Unspecified vulnerabilities in Zen Cart before 1.2.7 allow remote attackers to cause unknown impact via unspecified vectors related to "other attempted exploits" other than SQL injection.

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

It affects 1 product.


Products: Zen Cart Zen Cart.

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

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

## Is CVE-2006-0698 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3597](https://insights.sbomify.com/CVE-2007-3597/): Auth bypass in n/a (high 8.5)
- [CVE-2006-4214](https://insights.sbomify.com/CVE-2006-4214/): SQL injection in n/a (high 7.5)
- [CVE-2006-4218](https://insights.sbomify.com/CVE-2006-4218/): Path traversal in n/a (high 7.5)
- [CVE-2006-0696](https://insights.sbomify.com/CVE-2006-0696/): SQL injection in n/a (high 7.5)
- [CVE-2004-2023](https://insights.sbomify.com/CVE-2004-2023/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0698 is a critical vulnerability in n/a, published on 15 Feb 2006. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-0698 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-2006-0698/ (Markdown: https://insights.sbomify.com/CVE-2006-0698/index.md)
```

## Sources

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

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