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

> Remote attackers can include arbitrary files via directory traversal in the pmv_ck_view cookie, potentially leading to data exposure or code execution.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 12 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-66r6-2rhj-83mg

## What is CVE-2007-0893?

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

### Official description

Directory traversal vulnerability in phpMyVisites before 2.2 allows remote attackers to include arbitrary files via leading ".." sequences on the pmv_ck_view COOKIE parameter, which bypasses the protection scheme.

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

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

It affects 1 product.


Products: Matthieu Aubry Phpmyvisites.

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

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

## Is CVE-2007-0893 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0892](https://insights.sbomify.com/CVE-2007-0892/): Other in n/a (high 7.5)
- [CVE-2005-1325](https://insights.sbomify.com/CVE-2005-1325/): Path traversal in n/a (medium 5.0)
- [CVE-2007-0891](https://insights.sbomify.com/CVE-2007-0891/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-1324](https://insights.sbomify.com/CVE-2005-1324/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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