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

> Remote attackers can include arbitrary files via directory traversal in phpKF-Portal, potentially leading to data exposure or code execution.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jp75-4xf8-w783

## What is CVE-2008-6516?

CVE-2008-6516 is a high-severity path traversal vulnerability in n/a, published on 25 Mar 2009. It can be exploited over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in phpKF-Portal 1.10 allow remote attackers to include arbitrary files via a .. (dot dot) in the (1) tema_dizin parameter to baslik.php and (2) portal_ayarlarportal_dili parameter to anket_yonetim.php.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

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

It affects 1 product.


Products: Phpkf Phpkf-Portal.

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

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

## Is CVE-2008-6516 being exploited?

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

Public exploit code:

- PHPKF-Portal 1.10 - 'baslik.php?tema_dizin' Traversal Local File Inclusion (exploitdb)
- PHPKF-Portal 1.10 - 'anket_yonetim.php?portal_ayarlarportal_dili' Traversal Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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