CVE-2026-30402
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in wgcloud v.2.3.7 and before allows a remote attacker to execute arbitrary code via the test connection function
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA command injection vulnerability in wgcloud v2.3.7 and earlier allows remote attackers to execute arbitrary OS commands via the test connection function. The feature likely accepts user-supplied input (such as hostnames, IPs, or connection parameters) and passes it unsafely to system shell execution without proper input sanitization or parameterized command construction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.3.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Wgcloud is installedSearch for wgcloud installation directories (commonly /opt/wgcloud, /home/wgcloud, or the application root where wgcloud-server.jar resides) and check for running processes containing 'wgcloud' or 'Wgcloud'.Affected if Wgcloud software is found running on the system.
-
Check installed Wgcloud versionLocate the version file or examine the wgcloud-server.jar manifest. Common paths include the installation root directory containing a version.txt or release notes, or run: java -jar wgcloud-server.jar --version if supported. Compare against affected range <= 2.3.7.Affected if The installed version is 2.3.7 or earlier.
-
Verify test connection feature is exposedIdentify if the administrative web interface is accessible (default port typically 8080 or 9000). Check if the test connection endpoint (usually under /host/test or /connection/test in the API) is reachable without authentication or with admin credentials.Affected if The test connection function is accessible via HTTP/HTTPS without additional network restrictions.
-
Check network accessibility of admin interfaceReview firewall rules (iptables, ufw, cloud security groups) and bind addresses in wgcloud configuration to determine if the admin interface is exposed to untrusted networks (Internet, DMZ, or user workstations).Affected if The wgcloud admin interface is bound to 0.0.0.0 or an IP accessible from untrusted networks.
-
Inspect for suspicious command execution indicatorsReview wgcloud server logs (通常在 logs/ 目录下) for entries containing unusual command patterns, external IP connections to the test endpoint, or spawning of unexpected system processes around the time of test connection usage.Affected if Logs show unexpected commands, unknown source IPs calling the test endpoint, or anomalous process creation.
You are affected if Wgcloud version 2.3.7 or earlier is running and its test connection feature is accessible from your network, particularly if exposed to untrusted hosts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a version beyond v2.3.7 that addresses the command injection vulnerability. Until then, restrict network access to the wgcloud administrative interface and disable or firewall the test connection function if possible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30402 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data