# CVE-2008-6158: Other in n/a

> Unspecified vulnerabilities in the w3blabor CMS admin backend allow remote attackers to potentially compromise the system.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qc8x-rw5v-cm3c

## What is CVE-2008-6158?

CVE-2008-6158 is a critical vulnerability in n/a, published on 17 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in the admin backend in w3b>cms (aka w3blabor CMS) before 3.2.0 have unknown impact and remote attack vectors.

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

It affects 1 product.


Products: W3bcms W3b\>cms.

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

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

## Is CVE-2008-6158 being exploited?

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

Public exploit code:

- w3blabor CMS 3.0.5 - Arbitrary File Upload / Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6158 is a critical vulnerability in n/a, published on 17 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6158 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-6158/ (Markdown: https://insights.sbomify.com/CVE-2008-6158/index.md)
```

## Sources

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

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