# CVE-2006-4078: Auth bypass in n/a

> Remote attackers can bypass authentication in DeluxeBB by manipulating the membercookie parameter, potentially gaining unauthorized access to user accounts.

- **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:** 11 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f665-qj55-6rrx

## What is CVE-2006-4078?

CVE-2006-4078 is a high-severity authentication bypass vulnerability in n/a, published on 11 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pm.php (aka the PM system) in DeluxeBB 1.08, and possibly earlier, allows remote attackers to bypass authentication by providing an arbitrary username in the membercookie cookie parameter.

## Which versions are affected by CVE-2006-4078?

It affects 1 product.


Products: Deluxebb Deluxebb.

## How do I fix CVE-2006-4078?

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

## Is CVE-2006-4078 being exploited?

There is no known exploitation of CVE-2006-4078 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-6237](https://insights.sbomify.com/CVE-2007-6237/): Auth bypass in n/a (critical 9.0)
- [CVE-2009-4465](https://insights.sbomify.com/CVE-2009-4465/): Information disclosure in n/a (high 7.5)
- [CVE-2009-1033](https://insights.sbomify.com/CVE-2009-1033/): SQL injection in n/a (high 7.5)
- [CVE-2008-2194](https://insights.sbomify.com/CVE-2008-2194/): SQL injection in n/a (high 7.5)
- [CVE-2006-5154](https://insights.sbomify.com/CVE-2006-5154/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4078 and fix it if it is affected.

What it is: CVE-2006-4078 is a high-severity authentication bypass vulnerability in n/a, published on 11 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4078 in the wild and no public exploit code.

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-2006-4078/ (Markdown: https://insights.sbomify.com/CVE-2006-4078/index.md)
```

## Sources

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

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