dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-7763

HIGH · 7.5 CVSS v3.1 Published 2024-10-24
Fix available
A fix is available. Upgrade to 24.0 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 2024.0.0,  an Authentication Bypass issue exists which allows an attacker to obtain encrypted user credentials.

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 2024.0.0 contain an authentication bypass vulnerability that allows attackers to circumvent authentication mechanisms and obtain encrypted user credentials. The specific bypass technique is not detailed in the available description, but the vulnerability enables unauthorized access to credential data.

MitigationUpgrade WhatsUp Gold to version 2024.0.0 or later to remediate this vulnerability. Additionally, consider resetting user credentials as a precautionary measure since encrypted credentials were potentially exposed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Check WhatsUp Gold version
    Open the WhatsUp Gold web interface, navigate to Administration > System Settings > System Information, or check the installation directory for a version file. You can also query the application via its built-in about page or API endpoint.
    Affected if The installed version is earlier than 24.0.0 or 2024.0.0
  2. Verify Windows installation path version
    Navigate to the WhatsUp Gold installation directory (commonly C:\Program Files\Progress\WhatsUp Gold) and locate the version information file or right-click the WhatsUpGold.exe file and view Properties > Details for the version number.
    Affected if File version shown is below 24.0.0 or 2024.0.0
  3. Check service banner via web request
    If the web interface is accessible remotely, examine the HTTP response headers or login page source for version information that may be exposed in the application.
    Affected if The displayed version is less than 24.0.0
  4. Confirm authentication interface exposure
    Determine if the WhatsUp Gold web interface (typically ports 80/443 or 8080/8443) is accessible from network segments outside the trusted internal network.
    Affected if The web authentication portal is externally accessible and the version is below 24.0.0

You are affected if your installed WhatsUp Gold version is earlier than 24.0.0 (or 2024.0.0), regardless of configuration, since the vulnerability allows bypassing authentication to access credential data.

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 24.0 or later
Fixed in 24.0
Interim mitigation

Upgrade WhatsUp Gold to version 2024.0.0 or later to remediate this vulnerability. Additionally, consider resetting user credentials as a precautionary measure since encrypted credentials were potentially exposed.

Recommended fix High confidence

WhatsUp Gold 24.0.0 (2024.0.0)

  1. Obtain WhatsUp Gold version 24.0.0 or later from the official Progress download portal at www.progress.com
  2. Review the official WhatsUp Gold 24.0.0 release notes for any specific upgrade prerequisites
  3. Ensure you have a complete backup of your current WhatsUp Gold installation and database
  4. Stop the WhatsUp Gold services before beginning the upgrade process
  5. Install WhatsUp Gold 24.0.0 using the standard upgrade installation method
  6. Start the WhatsUp Gold services after installation completes
  7. Verify the upgrade was successful by logging into the web interface
  8. Confirm that user credentials are now properly secured

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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