dbcve.org
Whatsup GoldApplication · Progress

CVE-2023-6368

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 23.1.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In WhatsUp Gold versions released before 2023.1, an API endpoint was found to be missing an authentication mechanism. It is possible for an unauthenticated attacker to enumerate information related to a registered device being monitored by WhatsUp Gold.

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 confidence

WhatsUp Gold versions before 2023.1 contain an API endpoint that lacks authentication enforcement. An unauthenticated remote attacker can exploit this by sending requests to the endpoint to enumerate information about registered devices being monitored by the WhatsUp Gold installation, potentially revealing device names, IP addresses, status, and other monitoring metadata.

MitigationUpgrade WhatsUp Gold to version 2023.1 or later to obtain the patched release. If immediate upgrade is not feasible, implement network-level access controls to restrict the affected API endpoint to trusted IP addresses only.

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
Whatsup GoldApplication
Affected:< 23.1.0

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WhatsUp Gold is installed
    Check for the presence of WhatsUp Gold installation directories or the 'WhatsUp Gold' Windows service using Services.msc or the command: Get-Service | Where-Object {$_.DisplayName -like '*WhatsUp*'}
    Affected if WhatsUp Gold is present on the system
  2. Determine the installed WhatsUp Gold version
    Locate the application version information - typically found in the application UI under Help > About, or check the installation directory for version files. Compare your installed version to the affected range (versions before 23.1.0)
    Affected if The installed version is earlier than 23.1.0
  3. Identify network exposure of the WhatsUp Gold web interface
    Check if the WhatsUp Gold web interface (typically running on ports 80/443 or custom ports) is accessible from untrusted networks. Use network scanning tools or review firewall rules to determine external accessibility
    Affected if The web interface is reachable from untrusted or external networks
  4. Verify if the API endpoint requires authentication
    Attempt to access common WhatsUp Gold API paths (such as /api/* or /NMConsole/api/*) without providing credentials. If the endpoint returns device information or monitoring data without redirecting to a login page, authentication is not enforced
    Affected if The API endpoint returns data without requiring authentication credentials

You are affected if WhatsUp Gold version is before 23.1.0 AND the API endpoint is network-accessible without authentication enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 23.1.0 or later
Fixed in 23.1.0
Interim mitigation

Upgrade WhatsUp Gold to version 2023.1 or later to obtain the patched release. If immediate upgrade is not feasible, implement network-level access controls to restrict the affected API endpoint to trusted IP addresses only.

Recommended fix High confidence

WhatsUp Gold 23.1.0

  1. Upgrade WhatsUp Gold to version 23.1.0 (also known as 2023.1) or later to resolve the missing authentication vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6368 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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