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

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

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-536w-2hpc-2qvf

## What is CVE-2008-6833?

CVE-2008-6833 is a critical path traversal vulnerability in n/a, published on 22 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in commsrss.php in fuzzylime (cms) before 3.01b allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in a files array element for a blogs action, as demonstrated by the files[0] parameter.

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

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

It affects 1 product.


Products: Fuzzylime Fuzzylime \(Cms\).

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

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

## Is CVE-2008-6833 being exploited?

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

Public exploit code:

- Fuzzylime CMS 3.01 - 'commrss.php' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6834](https://insights.sbomify.com/CVE-2008-6834/): Path traversal in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6833 is a critical path traversal vulnerability in n/a, published on 22 Jun 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-6833 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-6833/ (Markdown: https://insights.sbomify.com/CVE-2008-6833/index.md)
```

## Sources

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

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