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

> Remote attackers can read arbitrary files via directory traversal in the order parameter, though the vulnerability's validity is disputed.

- **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:** 22 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5hjh-923j-ff4c

## What is CVE-2007-1601?

CVE-2007-1601 is a medium-severity path traversal vulnerability in n/a, published on 22 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in check_vote.php in Weekly Drawing Contest 0.0.1 allows remote attackers to read arbitrary files via a .. (dot dot) in the order parameter.  NOTE: another researcher disputes this vulnerability, noting that the order variable is not used in any context that allows opening files

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

It affects 1 product.


Products: Weekly Drawing Contest Weekly Drawing Contest.

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

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

## Is CVE-2007-1601 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1602](https://insights.sbomify.com/CVE-2007-1602/): SQL injection in n/a (high 7.5)
- [CVE-2007-1603](https://insights.sbomify.com/CVE-2007-1603/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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