# CVE-2006-5737: Weak cryptography in n/a

> Predictable cookie seeds allow attackers to forge admin sessions and take over accounts in PunBB forums.

- **Severity:** High 7.2 (`AV:L/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:** 6 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9fgm-w9px-m6vp

## What is CVE-2006-5737?

CVE-2006-5737 is a high-severity vulnerability in n/a, published on 6 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PunBB uses a predictable cookie_seed value that can be derived from the time of registration of the superadmin account (installation time), which might allow local users to perform unauthorized actions.

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

It affects 1 product.


Products: Punbb Punbb.

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

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

## Is CVE-2006-5737 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3335](https://insights.sbomify.com/CVE-2008-3335/): Command injection in n/a (critical 10.0)
- [CVE-2006-1090](https://insights.sbomify.com/CVE-2006-1090/): Denial of service in n/a (high 7.8)
- [CVE-2007-2234](https://insights.sbomify.com/CVE-2007-2234/): SQL injection in n/a (high 7.5)
- [CVE-2006-5735](https://insights.sbomify.com/CVE-2006-5735/): Path traversal in n/a (high 7.5)
- [CVE-2005-3518](https://insights.sbomify.com/CVE-2005-3518/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5737 is a high-severity vulnerability in n/a, published on 6 Nov 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-5737 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-5737/ (Markdown: https://insights.sbomify.com/CVE-2006-5737/index.md)
```

## Sources

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

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