# CVE-2006-0921: Path traversal in n/a

> Remote attackers can list and create arbitrary directories via path traversal in FCKeditor's connector.php, affecting file management integrity.

- **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:** 28 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m5r8-hrmj-57qg

## What is CVE-2006-0921?

CVE-2006-0921 is a medium-severity path traversal vulnerability in n/a, published on 28 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in connector.php in FCKeditor 2.0 FC, as used in products such as RunCMS, allow remote attackers to list and create arbitrary directories via a .. (dot dot) in the CurrentFolder parameter to (1) GetFoldersAndFiles and (2) CreateFolder.

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

It affects 1 product.


Products: Fckeditor Fckeditor.

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

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

## Is CVE-2006-0921 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2265](https://insights.sbomify.com/CVE-2009-2265/): Path traversal in n/a (high 7.5)
- [CVE-2008-6178](https://insights.sbomify.com/CVE-2008-6178/): File upload in n/a (high 7.5)
- [CVE-2006-2529](https://insights.sbomify.com/CVE-2006-2529/): File upload in n/a (medium 5.0)
- [CVE-2006-0658](https://insights.sbomify.com/CVE-2006-0658/): File upload in n/a (medium 5.0)
- [CVE-2005-0613](https://insights.sbomify.com/CVE-2005-0613/): File upload in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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