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

> Unspecified vulnerability in Exponent CMS allows remote attackers to exploit variables that are not typecasted.

- **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:** 4 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p457-mr62-5g69

## What is CVE-2006-1604?

CVE-2006-1604 is a critical vulnerability in n/a, published on 4 Apr 2006. It can be exploited over the network.

### Official description

Unspecified vulnerability in Exponent CMS before 0.96.5 RC 1 has unknown impact and remote attack vectors related to variables that are not "typecasted."

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

It affects 1 product.


Products: Exponent Exponent Cms.

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

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

## Is CVE-2006-1604 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1605](https://insights.sbomify.com/CVE-2006-1605/): Code injection in n/a (high 7.5)
- [CVE-2006-1607](https://insights.sbomify.com/CVE-2006-1607/): Code injection in n/a (high 7.5)
- [CVE-2006-4963](https://insights.sbomify.com/CVE-2006-4963/): Path traversal in n/a (medium 6.4)
- [CVE-2007-2252](https://insights.sbomify.com/CVE-2007-2252/): Path traversal in n/a (medium 5.0)
- [CVE-2007-2253](https://insights.sbomify.com/CVE-2007-2253/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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