CVE-2024-46907
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 · moderate confidenceA SQL injection vulnerability in WhatsUp Gold versions before 2024.0.1 allows authenticated users with at least Report Viewer permissions to inject malicious SQL queries, enabling privilege escalation to admin-level 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 installed WhatsUp Gold versionLocate the WhatsUp Gold installation directory and check the version information, typically found in the application GUI under Help > About or in installation logs and registry entriesAffected if The installed version is lower than 24.0.1 or 2024.0.1
-
Verify Report Viewer role exists and is assignedAccess the WhatsUp Gold admin console and navigate to User Management or Roles configuration to list all defined roles and their membershipsAffected if The Report Viewer role is defined and assigned to any non-admin users
-
Confirm reporting module is enabledCheck the WhatsUp Gold configuration to determine if the reporting functionality is active and accessibleAffected if The reporting module is enabled and accessible to users with Report Viewer permissions
-
Review user accounts with Report Viewer accessExport or review the user account list from the admin console to identify which accounts hold Report Viewer permissionsAffected if There are authenticated users assigned the Report Viewer role who are not already administrators
-
Audit SQL query logging for the reporting interfaceEnable and review database query logs or SQL tracing when the reporting feature is accessed by users with Report Viewer permissionsAffected if Unusual or malformed SQL queries appear in logs originating from the reporting interface
You are affected if running WhatsUp Gold version below 24.0.1 and the reporting feature is accessible to authenticated users with Report Viewer permissions, allowing them to inject malicious SQL and potentially escalate to admin-level access.
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 to obtain the vendor patch. Until then, restrict Report Viewer permissions to the minimum necessary users and monitor database activity for suspicious queries.
WhatsUp Gold 24.0.1 or later
- Download WhatsUp Gold version 24.0.1 or later from the official Progress website or customer portal
- Back up the current WhatsUp Gold database and configuration files
- Stop the WhatsUp Gold services before performing the upgrade
- Run the installer for version 24.0.1 or later
- Follow the installation wizard prompts to complete the upgrade
- Restart the WhatsUp Gold services after the upgrade completes
- Verify the upgrade was successful by logging into the web interface
- Confirm that the SQL injection vulnerability is no longer present by testing with a low-privileged Report Viewer account
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46907 — 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-46907 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