# CVE-2026-15732: WGDashboard Server-Side Request Forgery Vulnerability

> Authenticated attackers can exploit a webhook flaw in WGDashboard to perform server-side request forgery and retrieve arbitrary HTTP responses.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-89hj-33q6-8644

## What is CVE-2026-15732?

CVE-2026-15732 is a critical server-side request forgery vulnerability in WGDashboard, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSFR) vulnerability exist in WGDashboard version 4.2.3 and earlier. The webhook functionality allows authenticated attackers to make arbitrary HTTP requests and retrieve responses.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-15732?


## How do I fix CVE-2026-15732?

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

## Is CVE-2026-15732 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15732 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15732 and fix it if it is affected.

What it is: CVE-2026-15732 is a critical server-side request forgery vulnerability in WGDashboard, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15732 exists.

Affected product: WGDashboard. 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-2026-15732/ (Markdown: https://insights.sbomify.com/CVE-2026-15732/index.md)
```

## Sources

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

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