# CVE-2007-6233: Path traversal in n/a

> Authenticated attackers can exploit a directory traversal flaw in FTP Admin to include and execute arbitrary local files, potentially leading to remote code execution.

- **Severity:** Medium 4.9 (`AV:N/AC:M/Au:S/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:** 4 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g53c-h2hg-gwm4

## What is CVE-2007-6233?

CVE-2007-6233 is a medium-severity path traversal vulnerability in n/a, published on 4 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in FTP Admin 0.1.0 allows remote authenticated users to include and execute arbitrary local files via a .. (dot dot) in the page parameter.  NOTE: in some environments, this can be leveraged for remote file inclusion by using a UNC share pathname or an ftp, ftps, or ssh2.sftp URL.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2007-6233?

It affects 1 product.


Products: Ftp Admin Ftp Admin.

## How do I fix CVE-2007-6233?

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

## Is CVE-2007-6233 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6233 exists.

Public exploit code:

- ftp Admin 0.1.0 - Local File Inclusion / Cross-Site Scripting / Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6234](https://insights.sbomify.com/CVE-2007-6234/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6233 and fix it if it is affected.

What it is: CVE-2007-6233 is a medium-severity path traversal vulnerability in n/a, published on 4 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6233 exists.

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-2007-6233/ (Markdown: https://insights.sbomify.com/CVE-2007-6233/index.md)
```

## Sources

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

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