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

> Remote attackers can read source code and potentially traverse directories in Webfwlog when register_globals is enabled.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g6xg-84x8-m9p2

## What is CVE-2007-0585?

CVE-2007-0585 is a critical path traversal vulnerability in n/a, published on 30 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

include/debug.php in Webfwlog 0.92 and earlier, when register_globals is enabled, allows remote attackers to obtain source code of files via the conffile parameter.  NOTE: some of these details are obtained from third party information.  It is likely that this issue can be exploited to conduct directory traversal attacks.

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

It affects 1 product.


Products: Webfwlog Webfwlog.

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

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

## Is CVE-2007-0585 being exploited?

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

Public exploit code:

- Webfwlog 0.92 - 'debug.php' Remote File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0585 is a critical path traversal vulnerability in n/a, published on 30 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0585 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-0585/ (Markdown: https://insights.sbomify.com/CVE-2007-0585/index.md)
```

## Sources

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

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