dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Oct 2024. Known ransomware use
Whatsup GoldApplication · Progress

CVE-2024-6670

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
In the wild Ransomware High EPSS 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, 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

A pre-authentication SQL injection vulnerability in WhatsUp Gold versions prior to 2024.0.0 allows remote, unauthenticated attackers to execute arbitrary SQL queries. The vulnerability is in the authentication component, enabling retrieval of encrypted user password hashes from the database.

MitigationUpgrade to WhatsUp Gold 2024.0.0 or later immediately. As an interim control, restrict network access to the WhatsUp Gold interface and consider deploying a WAF with SQL injection rules.

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

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 WhatsUp Gold version
    Locate the WhatsUp Gold installation and check the version number (typically available in the web interface footer, installation directory, or product about page)
    Affected if The installed version is less than 24.0.0 (any version before 24.0)
  2. Verify network accessibility of web interface
    Determine if the WhatsUp Gold web interface (ports 80/443 or custom configured) is exposed to untrusted networks or the public internet
    Affected if The web interface is reachable from untrusted networks without proper network segmentation or authentication barriers
  3. Review database query logs
    Examine WhatsUp Gold database logs or SQL Server/PostgreSQL logs for unexpected or suspicious SQL queries, especially those selecting from user-related tables
    Affected if Unusual SQL queries containing UNION statements, or queries targeting user/password tables appear in logs
  4. Check for unauthorized database access
    Inspect the database for any unexpected stored procedures, new user accounts, or modifications to existing user password hashes
    Affected if Password hash fields show unexpected changes, new admin accounts exist that were not created by legitimate administrators, or database shows evidence of external extraction

A user is affected if their WhatsUp Gold version is below 24.0.0 and the web interface is accessible to potential attackers, allowing unauthenticated SQL injection to extract password hashes.

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 to WhatsUp Gold 2024.0.0 or later immediately. As an interim control, restrict network access to the WhatsUp Gold interface and consider deploying a WAF with SQL injection rules.

Recommended fix High confidence

WhatsUp Gold 24.0.0 (or 2024.0.0)

  1. Backup the WhatsUp Gold installation and its database before starting the upgrade process
  2. Review the WhatsUp Gold 24.0.0 release notes for any specific upgrade requirements or注意事项
  3. Download WhatsUp Gold version 24.0.0 or later from the Progress Customer Portal or official download渠道
  4. Upgrade the WhatsUp Gold installation to version 24.0.0 following the standard upgrade documentation
  5. After upgrade, verify that the SQL injection vulnerability is remediated by confirming the patched code is in place
  6. Test that the WhatsUp Gold web interface and API endpoints function normally after the upgrade
Caveat Review release notes for any configuration or feature changes between your current version and 24.0.0; test in non-production environment first

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

Fix this in Whatsup Gold Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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