# CVE-2008-1766: Multiple unspecified vulnerabilities in phpBB before 3.0.1 have unknown impact and attack vectors, related to "two minor security-related bu


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wj97-45j5-j24v

## What is CVE-2008-1766?

CVE-2008-1766 is a critical vulnerability in n/a, published on 12 Apr 2008. 

### Official description

Multiple unspecified vulnerabilities in phpBB before 3.0.1 have unknown impact and attack vectors, related to "two minor security-related bugs."

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

It affects 1 product.


Products: Phpbb Phpbb.

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

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

## Is CVE-2008-1766 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3224](https://insights.sbomify.com/CVE-2008-3224/): Other in n/a (critical 10.0)
- [CVE-2025-70810](https://insights.sbomify.com/CVE-2025-70810/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2001-1471](https://insights.sbomify.com/CVE-2001-1471/): Code injection in n/a (high 8.8)
- [CVE-2026-29199](https://insights.sbomify.com/CVE-2026-29199/): phpBB has Password Reset Link Poisoning via Host Header injection (high 8.1)
- [CVE-2019-16108](https://insights.sbomify.com/CVE-2019-16108/): phpBB arbitrary CSS injection (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1766 is a critical vulnerability in n/a, published on 12 Apr 2008. 
Exploitation: There is no known exploitation of CVE-2008-1766 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-2008-1766/ (Markdown: https://insights.sbomify.com/CVE-2008-1766/index.md)
```

## Sources

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

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