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

> Remote attackers can read arbitrary files in Facil CMS via directory traversal in index.php or modules.php parameters.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jj65-xh5q-x5mf

## What is CVE-2008-7176?

CVE-2008-7176 is a medium-severity path traversal vulnerability in n/a, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Facil CMS 0.1RC allow remote attackers to read arbitrary files via a .. (dot dot) in the (1) change_lang parameter to index.php or (2) modload parameter to modules.php.

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

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

It affects 1 product.


Products: Celina Jorge Facil Cms.

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

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

## Is CVE-2008-7176 being exploited?

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

Public exploit code:

- Facil-CMS 0.1RC - Multiple Local File Inclusions (exploitdb)
- Facil-CMS 0.1RC2 - Local/Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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