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

> Remote attackers can read sensitive files via path traversal in the file parameter of download.php in JV2 Folder Gallery.

- **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:** 18 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9xc3-v42x-896q

## What is CVE-2007-0329?

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

### Official description

download.php in Joonas Viljanen JV2 Folder Gallery allows remote attackers to read sensitive files via a relative pathname in the file parameter, as demonstrated by config/gallerysetup.php.  NOTE: this issue might be resultant from a directory traversal vulnerability.

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

It affects 1 product.


Products: Joonas Viljanen Jv2 Folder Gallery.

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

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

## Is CVE-2007-0329 being exploited?

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

Public exploit code:

- JV2 Folder Gallery 3.0 - 'download.php' Remote File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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