# CVE-2025-8066: Bunker Web 1.6.2 - Uncontrolled external site redirect

> An open redirect vulnerability in Bunker Web allows attackers to redirect users to malicious sites, facilitating phishing attacks.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 15 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-p2gr-8xqx-rxmg

## What is CVE-2025-8066?

CVE-2025-8066 is a medium-severity vulnerability in Bunkerity Bunker Web, published on 15 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Bunkerity Bunker Web on Linux allows Phishing.This issue affects Bunker Web: 1.6.2.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-8066?


## How do I fix CVE-2025-8066?

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

## Is CVE-2025-8066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8066 and fix it if it is affected.

What it is: CVE-2025-8066 is a medium-severity vulnerability in Bunkerity Bunker Web, published on 15 Aug 2025. 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-2025-8066 in the wild and no public exploit code.

Affected product: Bunkerity Bunker Web. 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-2025-8066/ (Markdown: https://insights.sbomify.com/CVE-2025-8066/index.md)
```

## Sources

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

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