dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-6671

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 24.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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, if the application is configured with only a single user, a SQL Injection vulnerability allows an unauthenticated attacker to retrieve the users encrypted password.

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.0 allows unauthenticated attackers to retrieve a user's encrypted password when the application is configured with only a single user account. The critical severity (CVSS 9.8) reflects the ability to exploit this without authentication and obtain sensitive credential material.

MitigationUpgrade WhatsUp Gold to version 2024.0.0 or later. As a defensive measure, avoid single-user configurations and implement proper network segmentation to limit exposure.

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:>= 23.1.0, < 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed WhatsUp Gold version
    Access the WhatsUp Gold admin interface and navigate to the About or System Information section, or check the version information in the installation directory documentation
    Affected if The version displayed is 23.1.0 or higher but lower than 24.0
  2. Verify user account configuration
    In the WhatsUp Gold admin interface, navigate to User Management or Administration > Users to count the number of configured user accounts
    Affected if Only a single user account is configured in the system
  3. Confirm SQL injection exposure
    This vulnerability is exploitable via the web interface without authentication; check if the application login page or user authentication endpoints are directly exposed to untrusted networks
    Affected if The WhatsUp Gold web interface is accessible from untrusted networks and the application uses single-user configuration
  4. Check for password hash retrieval capability
    Review application logs for any unexpected SQL queries or authentication anomalies that may indicate exploitation attempts targeting user credential retrieval
    Affected if Unusual SQL-related errors or authentication anomalies appear in logs related to password retrieval queries

A user is affected if their WhatsUp Gold installation version is between 23.1.0 and 24.0 (exclusive) AND the application is configured with exactly one user account.

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. As a defensive measure, avoid single-user configurations and implement proper network segmentation to limit exposure.

Recommended fix High confidence

WhatsUp Gold 24.0

  1. Download WhatsUp Gold version 24.0 or later from the official Progress website or your authorized distribution channel
  2. Review the WhatsUp Gold 24.0 release notes and upgrade documentation
  3. Create a complete backup of your current WhatsUp Gold installation, including the database and configuration files
  4. Stop the WhatsUp Gold services before upgrading
  5. Install WhatsUp Gold 24.0 following the standard upgrade procedure
  6. After installation, verify that the single-user configuration still works correctly
  7. Confirm the SQL injection vulnerability is no longer present by verifying the fix is applied
Caveat Review release notes for any configuration or feature changes between your current version and 24.0

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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