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

> Remote attackers can read or overwrite arbitrary files and create directories in Chupix CMS via directory traversal in download.php.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6rfx-645f-j638

## What is CVE-2007-4957?

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

### Official description

Multiple directory traversal vulnerabilities in download.php in Chupix CMS 0.2.3 allow remote attackers to read or overwrite arbitrary files via a .. (dot dot) in the (1) fichier or (2) repertoire parameter, or create arbitrary directories via a .. (dot dot) in the (3) repertoire parameter.

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

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

It affects 1 product.


Products: Chupix Chupix Cms.

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

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

## Is CVE-2007-4957 being exploited?

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

Public exploit code:

- Chupix CMS 0.2.3 - 'download.php' Remote File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5139](https://insights.sbomify.com/CVE-2007-5139/): Code injection in n/a (medium 6.8)
- [CVE-2008-3562](https://insights.sbomify.com/CVE-2008-3562/): Path traversal in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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