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

> Authenticated attackers can exploit a directory traversal flaw in Post Affiliate Pro to read or execute arbitrary local files.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-99qf-p549-mmhm

## What is CVE-2008-4602?

CVE-2008-4602 is a medium-severity path traversal vulnerability in n/a, published on 17 Oct 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in Post Affiliate Pro 2.0 allows remote authenticated users to read and possibly execute arbitrary local files via a .. (dot dot) in the md parameter.

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

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

It affects 1 product.


Products: Qualityunit Post Affiliate Pro.

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

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

## Is CVE-2008-4602 being exploited?

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

Public exploit code:

- Post Affiliate Pro 2.0 - 'md' Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5630](https://insights.sbomify.com/CVE-2008-5630/): SQL injection in n/a (medium 6.8)
- [CVE-2023-38482](https://insights.sbomify.com/CVE-2023-38482/): WordPress Post Affiliate Pro Plugin <= 1.25.0 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4602 is a medium-severity path traversal vulnerability in n/a, published on 17 Oct 2008. Any signed-in user can exploit it 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-4602 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-4602/ (Markdown: https://insights.sbomify.com/CVE-2008-4602/index.md)
```

## Sources

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

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