dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-46905

HIGH · 8.8 CVSS v3.1 Published 2024-12-02
Fix available
A fix is available. Upgrade to 24.0.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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.1, a SQL Injection vulnerability allows an authenticated lower-privileged user (at least Network Manager permissions required) to achieve privilege escalation to the admin account.

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

SQL injection vulnerability in WhatsUp Gold versions before 2024.0.1 allows authenticated users with Network Manager-level permissions to inject malicious SQL queries, enabling privilege escalation to obtain admin account access.

MitigationUpgrade WhatsUp Gold to version 2024.0.1 or later to patch the SQL injection vulnerability.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify if WhatsUp Gold is installed
    Check for WhatsUp Gold installation directories (commonly in C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold) or look for the 'WhatsUp Gold' Windows service.
    Affected if WhatsUp Gold is installed on the system.
  2. Determine the installed version
    Locate the WhatsUp Gold version file or check the web interface login page footer which typically displays the version number. Compare against the affected range (versions before 24.0.1).
    Affected if The installed version is prior to 24.0.1.
  3. Verify Network Manager-level accounts exist
    Access the WhatsUp Gold admin interface and review user accounts in the user management section. Look for accounts assigned the 'Network Manager' role or equivalent high-privilege permissions.
    Affected if There are user accounts with Network Manager-level permissions in the system.
  4. Confirm web interface accessibility
    Attempt to access the WhatsUp Gold web console (typically on ports 80/443 or 8080/8443). Verify the login page is reachable.
    Affected if The WhatsUp Gold web interface is accessible from the network.

A user is affected if WhatsUp Gold version 24.0.1 or later is not installed AND the web interface is accessible to authenticated users with Network Manager-level permissions.

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.1 or later
Fixed in 24.0.1
Interim mitigation

Upgrade WhatsUp Gold to version 2024.0.1 or later to patch the SQL injection vulnerability.

Recommended fix High confidence

WhatsUp Gold 24.0.1 or later

  1. 1. Create a complete backup of the WhatsUp Gold database and configuration files.
  2. 2. Verify backup integrity before proceeding with the upgrade.
  3. 3. Download WhatsUp Gold version 24.0.1 or later from the official Progress website (www.progress.com).
  4. 4. Review the official upgrade documentation at docs.progress.com for version-specific upgrade instructions.
  5. 5. Execute the installer for version 24.0.1, following the on-screen prompts.
  6. 6. After upgrade completion, verify the installation was successful.
  7. 7. Confirm that the SQL injection vulnerability is no longer present by testing with a non-admin user (Network Manager role).
  8. 8. Validate that all normal monitoring functionality remains operational after the upgrade.

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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