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

> Remote attackers can execute arbitrary local files via directory traversal in the cm_imgpath parameter of Phprojekt CMS.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-32xm-mv3c-fjjv

## What is CVE-2008-2217?

CVE-2008-2217 is a medium-severity path traversal vulnerability in n/a, published on 14 May 2008. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in cm/graphie.php in Content Management System 0.6.1 for Phprojekt allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the cm_imgpath parameter.

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

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

It affects 1 product.


Products: Mario Valdez Content Management System.

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

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

## Is CVE-2008-2217 being exploited?

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

Public exploit code:

- Content Management System for Phprojekt 0.6.1 - File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2217 is a medium-severity path traversal vulnerability in n/a, published on 14 May 2008. It can be exploited 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-2217 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-2217/ (Markdown: https://insights.sbomify.com/CVE-2008-2217/index.md)
```

## Sources

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

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