dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-46908

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 low-privileged user (at least Report Viewer 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

A SQL Injection vulnerability in WhatsUp Gold versions prior to 2024.0.1 allows an authenticated user with Report Viewer permissions to inject malicious SQL queries, potentially escalating privileges to admin level by manipulating database queries through the reporting interface.

MitigationUpgrade WhatsUp Gold to version 2024.0.1 or later to obtain the patched version. If immediate upgrade is not possible, restrict Report Viewer permissions to trusted users only and monitor database activity for suspicious queries.

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 the installed WhatsUp Gold version
    Locate the installed version of WhatsUp Gold in the system (typically accessible via the application UI, About section, or installed programs list)
    Affected if The installed version is any release prior to 24.0.1 (2024.0.1)
  2. Determine if Report Viewer permissions are configured
    Access the WhatsUp Gold administration interface and review user role permissions, specifically looking for the Report Viewer role or permission set
    Affected if The Report Viewer role or permission exists and is assigned to any user account
  3. Confirm authenticated access to the reporting interface
    Verify that users with Report Viewer permissions can access the reporting functionality through the web interface or application
    Affected if The reporting interface is accessible to authenticated users with Report Viewer permissions
  4. Review user accounts with elevated privileges
    Examine the list of users who have both Report Viewer permissions and assess whether any non-admin accounts exist in the system
    Affected if Any authenticated user with Report Viewer permissions exists who is not already designated as an administrator

Your environment is affected if WhatsUp Gold version is below 24.0.1 AND the Report Viewer role is accessible to authenticated users in your deployment

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 obtain the patched version. If immediate upgrade is not possible, restrict Report Viewer permissions to trusted users only and monitor database activity for suspicious queries.

Recommended fix High confidence

WhatsUp Gold 24.0.1

  1. Back up your WhatsUp Gold database and configuration files before upgrading.
  2. Download WhatsUp Gold version 24.0.1 or later from the official Progress website (community.progress.com or www.progress.com).
  3. Stop the WhatsUp Gold services to ensure a clean upgrade process.
  4. Run the WhatsUp Gold installer and follow the on-screen upgrade wizard instructions.
  5. Complete the installation and restart the WhatsUp Gold services.
  6. Verify the upgrade was successful by checking the WhatsUp Gold version in the console.
  7. Confirm that the SQL injection vulnerability is resolved by verifying that low-privileged users (Report Viewer role) can no longer escalate privileges to admin.
Caveat Review release notes for any configuration or feature changes between your current version and 24.0.1 before upgrading.

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

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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