dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5013

HIGH · 7.5 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
84/100
Remediation priority · High
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.3, an unauthenticated Denial of Service vulnerability was identified. An unauthenticated attacker can put the application into the SetAdminPassword installation step, which renders the application non-accessible.

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 · high confidence

An unauthenticated Denial of Service vulnerability in WhatsUp Gold versions before 2023.1.3 allows attackers to manipulate the application into entering the SetAdminPassword installation step, which renders the entire application inaccessible to legitimate users.

MitigationUpgrade to WhatsUp Gold version 2023.1.3 or later. Additionally, restrict network access to installation/setup endpoints using firewall rules or network segmentation to prevent unauthorized triggering of the installation workflow.

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.3

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Check installed WhatsUp Gold version
    Locate the WhatsUp Gold installation directory and find the version information, typically in an About section, version file, or installer log. Common locations include the program files directory or the web interface login page.
    Affected if The installed version is any version before 23.1.3 (e.g., 23.0.x, 22.x, or earlier)
  2. Verify application accessibility
    Attempt to access the WhatsUp Gold web interface. Try to reach the login page at the standard HTTPS port (typically 443 or 8443) for your installation.
    Affected if The login page is inaccessible, redirects to a password setup screen, or displays the SetAdminPassword installation step instead of normal login
  3. Check for installation workflow trigger
    Inspect the web interface for signs that the SetAdminPassword installation step has been activated. This typically presents as a password creation form when accessing the application.
    Affected if The application presents the SetAdminPassword or initial setup screen instead of the normal administrative login
  4. Review network exposure to setup endpoints
    Identify if the WhatsUp Gold web interface installation and setup URLs are exposed to untrusted networks. Check firewall rules allowing access to port 443/8443 from external or untrusted IP addresses.
    Affected if The installation/setup endpoints are accessible from untrusted networks without authentication

A user is affected if their installed WhatsUp Gold version is before 23.1.3 AND the application is either inaccessible or has been redirected to the SetAdminPassword installation screen.

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.3 or later
Fixed in 23.1.3
Interim mitigation

Upgrade to WhatsUp Gold version 2023.1.3 or later. Additionally, restrict network access to installation/setup endpoints using firewall rules or network segmentation to prevent unauthorized triggering of the installation workflow.

Recommended fix High confidence

WhatsUp Gold 23.1.3 or later (recommended: latest available stable release)

  1. Identify the current WhatsUp Gold version by checking the application or installation
  2. Navigate to the Progress Software customer portal or official download page
  3. Download WhatsUp Gold version 23.1.3 or later (preferably the latest stable release)
  4. Before upgrading, backup the current WhatsUp Gold configuration and database
  5. Execute the upgrade installer on the WhatsUp Gold server
  6. Follow the on-screen upgrade prompts to complete the installation
  7. Verify the application is accessible and functioning normally after upgrade
Caveat Standard upgrade precautions apply - backup before upgrading; test in non-production environment first if possible

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

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5013 — 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-2024-5013 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