# CVE-2006-6840: Other in n/a

> An unspecified vulnerability in phpBB allows remote attackers to exploit a negative start parameter, potentially leading to unknown impacts.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 3 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-88hw-xxc5-2mqg

## What is CVE-2006-6840?

CVE-2006-6840 is a critical vulnerability in Phpbb Group Phpbb, published on 3 Jan 2007. It can be exploited over the network.

### Official description

Unspecified vulnerability in phpBB before 2.0.22 has unknown impact and remote attack vectors related to a "negative start parameter."

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

It affects 1 product.


Products: Phpbb Group Phpbb.

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

Upgrade to a fixed version.

## Is CVE-2006-6840 being exploited?

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

## Other vulnerabilities in Phpbb Group Phpbb

- [CVE-2007-1695](https://insights.sbomify.com/CVE-2007-1695/): File upload in n/a (critical 10.0)
- [CVE-2006-6839](https://insights.sbomify.com/CVE-2006-6839/): Open redirect in n/a (critical 10.0)
- [CVE-2006-6841](https://insights.sbomify.com/CVE-2006-6841/): Cross-site request forgery in n/a (critical 10.0)
- [CVE-2002-2176](https://insights.sbomify.com/CVE-2002-2176/): SQL injection in n/a (critical 10.0)
- [CVE-2002-1537](https://insights.sbomify.com/CVE-2002-1537/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6840 is a critical vulnerability in Phpbb Group Phpbb, published on 3 Jan 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-6840 in the wild and no public exploit code.

Affected product: Phpbb Group Phpbb. 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-6840/ (Markdown: https://insights.sbomify.com/CVE-2006-6840/index.md)
```

## Sources

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

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