# CVE-2026-30404: Server-side request forgery in n/a

> An attacker can exploit an SSRF vulnerability in wgcloud's database connection test to probe internal networks and download malicious files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-rg9m-jxjw-mqj6

## What is CVE-2026-30404?

CVE-2026-30404 is a high-severity server-side request forgery vulnerability in n/a, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

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

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

It affects 1 product.


Products: Wgstart Wgcloud.

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

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

## Is CVE-2026-30404 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-30402](https://insights.sbomify.com/CVE-2026-30402/): Code injection in n/a (critical 9.8)
- [CVE-2026-30403](https://insights.sbomify.com/CVE-2026-30403/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30404 is a high-severity server-side request forgery vulnerability in n/a, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30404 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-2026-30404/ (Markdown: https://insights.sbomify.com/CVE-2026-30404/index.md)
```

## Sources

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

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