# CVE-2006-6841: Cross-site request forgery in n/a

> phpBB forms lack session checks, allowing attackers to perform actions on behalf of authenticated users via CSRF.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hwvv-5767-4qfp

## What is CVE-2006-6841?

CVE-2006-6841 is a critical vulnerability in Phpbb Group Phpbb, published on 3 Jan 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Certain forms in phpBB before 2.0.22 lack session checks, which has unknown impact and remote attack vectors.

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

It affects 1 product.


Products: Phpbb Group Phpbb.

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

Upgrade to a fixed version.

## Is CVE-2006-6841 being exploited?

There is no known exploitation of CVE-2006-6841 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-6840](https://insights.sbomify.com/CVE-2006-6840/): Other 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-6841 and fix it if it is affected.

What it is: CVE-2006-6841 is a critical vulnerability in Phpbb Group Phpbb, published on 3 Jan 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-6841 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-6841/ (Markdown: https://insights.sbomify.com/CVE-2006-6841/index.md)
```

## Sources

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

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