# CVE-2006-1851: Information disclosure in n/a

> Remote attackers can determine the application installation path via specific CGI parameters, exposing internal directory structures.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 19 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6w43-g48h-88v4

## What is CVE-2006-1851?

CVE-2006-1851 is a medium-severity vulnerability in n/a, published on 19 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

xFlow 5.46.11 and earlier allows remote attackers to determine the installation path of the application via the (1) action parameter to members_only/index.cgi and (2) page parameter customer_area/index.cgi, probably due to invalid values.

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

It affects 1 product.


Products: Skymarx Solutions Xflow.

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

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

## Is CVE-2006-1851 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1849](https://insights.sbomify.com/CVE-2006-1849/): SQL injection in n/a (high 7.5)
- [CVE-2006-1850](https://insights.sbomify.com/CVE-2006-1850/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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