# CVE-2008-0480: Path traversal in n/a

> Remote attackers can list arbitrary directories and files via path traversal in Web Wiz Forums, exposing sensitive file structures.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 29 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gfr7-vjm7-2h33

## What is CVE-2008-0480?

CVE-2008-0480 is a medium-severity path traversal vulnerability in n/a, published on 29 Jan 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Web Wiz Forums 9.07 and earlier allow remote attackers to list arbitrary directories, and .txt and .zip files, via a .....\\\ in the sub parameter to (1) RTE_file_browser.asp or (2) file_browser.asp.

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

## Which versions are affected by CVE-2008-0480?

It affects 1 product.


Products: Web Wiz Web Wiz Forums.

## How do I fix CVE-2008-0480?

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

## Is CVE-2008-0480 being exploited?

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

Public exploit code:

- Web Wiz Forums 9.07 - 'sub' Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0480 and fix it if it is affected.

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

## Sources

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

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