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

> Remote attackers can execute arbitrary local files via directory traversal in FOG Forum parameters, leading to code execution and data exposure.

- **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:** 3 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xffw-v379-pm86

## What is CVE-2008-2993?

CVE-2008-2993 is a high-severity path traversal vulnerability in n/a, published on 3 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in index.php in FOG Forum 0.8.1 allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the (1) fog_lang and (2) fog_skin parameters, probably related to libs/required/share.inc; and possibly the (3) fog_pseudo, (4) fog_posted, (5) fog_password, and (6) fog_cook parameters.

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

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

It affects 1 product.


Products: Fog Fog Forum.

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

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

## Is CVE-2008-2993 being exploited?

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

Public exploit code:

- FOG Forum 0.8.1 - Multiple Local File Inclusions (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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