CVE-2026-30404: wgcloud · Server-Side Request Forgery (SSRF)
Affects wgcloudSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubtianshiyeben/wgcloudpkg:github/tianshiyeben/wgcloudOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-30404 effectively, organizations should take the following specific actions: 1) Immediately restrict network access to the wgcloud backend database management connection test feature, ideally limiting it to trusted internal IP addresses or VPNs to prevent external exploitation. 2) Implement strict network segmentation to isolate wgcloud servers from sensitive internal resources, minimizing the impact of SSRF-based internal reconnaissance. 3) Monitor outbound traffic from wgcloud servers for unusual or unauthorized requests, particularly to internal IP ranges or external domains, using network intrusion detection systems or firewall logs. 4) Disable or remove the vulnerable connection test feature if it is not essential for operations, reducing the attack surface. 5) Engage with wgcloud vendors or community to obtain patches or updates addressing the SSRF vulnerability as soon as they become available. 6) Conduct regular security assessments and penetration tests focusing on SSRF and related web application vulnerabilities within the environment. 7) Educate system administrators and security teams about the risks of SSRF and the importance of applying network-level controls. These targeted measures go beyond generic advice by focusing on access control, monitoring, and feature management specific to the vulnerability context.
Description
The backend database management connection test feature in wgcloud v3.6.3 has a server-side request forgery (SSRF) vulnerability. This issue can be exploited to make the server send requests to probe the internal network, remotely download malicious files, and perform other dangerous operations.