CVE-2024-46906
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 · uneditedIn 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 confidenceA SQL Injection vulnerability in WhatsUp Gold versions before 2024.0.1 allows an authenticated user with at least Report Viewer permissions to inject malicious SQL queries, enabling privilege escalation from a low-privileged account to full admin access.
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< 24.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WhatsUp Gold installation and versionLocate the WhatsUp Gold installation directory and find the version information, typically in the main application folder or in the program files directory. Common locations include C:\Program Files\Progress\WhatsUp Gold or similar. Look for version.txt, a readme, or check the application properties.Affected if The installed version is before 24.0.1 (versions like 23.x, 22.x, or earlier)
-
Verify the Report Viewer role is assignedCheck user account permissions in WhatsUp Gold admin console. Navigate to User Management or Administration > Users and look for the Report Viewer role or permission group assignment.Affected if The user account has Report Viewer permissions or higher-level access (this role provides the minimum access needed to exploit the vulnerability)
-
Confirm reporting functionality is enabledCheck if the WhatsUp Gold reporting module or web interface reporting features are active. This can be verified through the admin console under Reports or Monitoring settings, or by confirming the reporting web service is running.Affected if Reporting features are enabled and accessible to the authenticated user with Report Viewer permissions
A user is affected if they run WhatsUp Gold versions before 24.0.1 and have an account with at least Report Viewer permissions, as the SQL injection can be exploited through the reporting interface to escalate privileges to admin.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.0.1
Upgrade WhatsUp Gold to version 2024.0.1 or later, or apply vendor-provided patches that address the SQL injection vulnerability.
24.0.1
- Obtain WhatsUp Gold version 24.0.1 or later from the official Progress download portal
- Review the official WhatsUp Gold 24.0.1 release notes for any specific upgrade prerequisites
- Back up the current WhatsUp Gold database and configuration files
- Ensure the upgrade is tested in a non-production environment before applying to production
- Execute the upgrade installer following Progress standard upgrade procedures
- Verify the upgrade was successful by checking the version number in the WhatsUp Gold interface
- Confirm the SQL injection vulnerability is no longer present by validating that low-privileged users cannot escalate privileges
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46906 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46906 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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