# CVE-2008-3192: Directory traversal vulnerability in index.php in jSite 1.0 OE allows remote attackers to include and execute arbitrary local files via a ..


- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wg6c-vw94-2hf7

## What is CVE-2008-3192?

CVE-2008-3192 is a medium-severity vulnerability in n/a, published on 16 Jul 2008. 

### Official description

Directory traversal vulnerability in index.php in jSite 1.0 OE allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the module parameter.

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

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

It affects 1 product.


Products: Sclek Jsite.

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

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

## Is CVE-2008-3192 being exploited?

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

Public exploit code:

- jsite 1.0 oe - SQL Injection / Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-7301](https://insights.sbomify.com/CVE-2008-7301/): SQL injection in n/a (high 7.5)
- [CVE-2008-3193](https://insights.sbomify.com/CVE-2008-3193/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3192 is a medium-severity vulnerability in n/a, published on 16 Jul 2008. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3192 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-3192/ (Markdown: https://insights.sbomify.com/CVE-2008-3192/index.md)
```

## Sources

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

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