# CVE-2006-5569: Hardcoded credentials in n/a

> Remote attackers can read or write arbitrary files using default testing accounts in FtpXQ Server.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2006
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gh3m-6hm9-f3rx

## What is CVE-2006-5569?

CVE-2006-5569 is a medium-severity vulnerability in n/a, published on 27 Oct 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FtpXQ Server 3.0.1 installs with two default testing accounts, which allows remote attackers to read or write arbitrary files via unknown vectors.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.

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

It affects 1 product.


Products: Datawizard Ftpxq.

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

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

## Is CVE-2006-5569 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1213](https://insights.sbomify.com/CVE-2001-1213/): Hardcoded credentials in n/a (medium 6.4)
- [CVE-2006-5568](https://insights.sbomify.com/CVE-2006-5568/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1920](https://insights.sbomify.com/CVE-2002-1920/): Memory corruption in n/a (medium 5.0)
- [CVE-2001-0293](https://insights.sbomify.com/CVE-2001-0293/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5569 is a medium-severity vulnerability in n/a, published on 27 Oct 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5569 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-5569/ (Markdown: https://insights.sbomify.com/CVE-2006-5569/index.md)
```

## Sources

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

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