PatchSiren cyber security CVE debrief
CVE-2026-15732 WGDashboard CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-06T22:16:48.300Z and has not been modified since then. A Server-Side Request Forgery (SSRF) vulnerability exists in WGDashboard version 4.2.3 and earlier. The webhook functionality allows authenticated attackers to make arbitrary HTTP requests and retrieve responses, potentially leading to sensitive information disclosure or further attacks. This vulnerability has a CVSS score of 9.8 and a severity of CRITICAL. WGDashboard users and administrators, security teams, and organizations using WGDashboard should be aware of this critical vulnerability and take immediate action to mitigate the risk.
- Vendor
- WGDashboard
- Product
- Unknown
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-06
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-08-06
- Advisory updated
- 2026-09-03
Who should care
WGDashboard users and administrators, security teams, and organizations using WGDashboard should be aware of this critical vulnerability and take immediate action to mitigate the risk. This includes reviewing and restricting webhook functionality, monitoring for suspicious HTTP requests, and implementing compensating controls to detect and prevent SSRF attacks.
Technical summary
A Server-Side Request Forgery (SSRF) vulnerability exists in WGDashboard version 4.2.3 and earlier. The webhook functionality allows authenticated attackers to make arbitrary HTTP requests and retrieve responses, potentially leading to sensitive information disclosure or further attacks. This vulnerability has a CVSS score of 9.8 and a severity of CRITICAL. The vulnerability can be exploited by authenticated attackers to make arbitrary HTTP requests and retrieve responses, which can lead to sensitive information disclosure or further attacks. Defenders should verify the presence of WGDashboard in their environment, review webhook configurations, and monitor for suspicious activity.
Defensive priority
Authenticated attackers can exploit this critical vulnerability to make arbitrary HTTP requests and retrieve responses, potentially leading to sensitive information disclosure or further attacks.
Recommended defensive actions
- Inventory WGDashboard installations to identify potential targets.
- Restrict webhook functionality to minimize exposure.
- Monitor for suspicious HTTP requests.
- Implement compensating controls to detect and prevent SSRF attacks.
- Apply vendor remediation when available.
Evidence notes
The vulnerability exists in WGDashboard version 4.2.3 and earlier, with a CVSS score of 9.8 and a severity of CRITICAL. The webhook functionality allows authenticated attackers to make arbitrary HTTP requests and retrieve responses. Evidence is limited to publicly available information and may not reflect the full scope of affected systems or potential impacts. Defenders should verify the presence of WGDashboard in their environment, review webhook configurations, and monitor for suspicious activity.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-15732 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-15732
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-15732 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-15732
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/Stuub/WGDashboard-v4.3.2-Full-Read-SSRF-via-Webhooks-PoC
-
Source reference
Unverified legacy reference
URL: https://github.com/WGDashboard/WGDashboard
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.