CVE-2024-6672
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.0, a SQL Injection vulnerability allows an authenticated low-privileged attacker to achieve privilege escalation by modifying a privileged user's 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 confidenceA SQL Injection vulnerability exists in WhatsUp Gold versions prior to 2024.0.0 that allows an authenticated low-privileged attacker to escalate privileges by modifying a privileged user's password through malicious SQL 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< 24.0CVSS 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 versionLocate the WhatsUp Gold installation and check the version number, typically found in the application UI under About or in the installation directory's version infoAffected if The installed version is less than 24.0 (or 2024.0.0)
-
Confirm web interface is accessibleVerify that the WhatsUp Gold web interface is reachable and accepts authenticationAffected if The web interface is exposed and users can authenticate, as the SQL injection requires an authenticated session to exploit
-
Review user account modificationsCheck audit logs or user management records for any password change events on privileged accounts performed by low-privileged usersAffected if Unexpected password modifications to administrator or other privileged accounts exist in logs
-
Inspect database query logsExamine SQL query logs or database audit trails for anomalous SQL syntax in password change operationsAffected if Logs contain SQL injection patterns or malformed queries in password modification contexts
You are affected if WhatsUp Gold version is below 24.0 and the application is accessible to authenticated users, as the vulnerability allows a low-privileged authenticated user to inject malicious SQL to modify privileged account passwords
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
Upgrade WhatsUp Gold to version 2024.0.0 or later to apply the vendor patch that addresses this SQL Injection vulnerability.
WhatsUp Gold 24.0.0 (2024.0.0)
- Backup the WhatsUp Gold database and configuration files before starting the upgrade
- Download WhatsUp Gold version 24.0.0 or later from the official Progress website (www.progress.com)
- Stop the WhatsUp Gold services to prepare for the upgrade
- Run the installer/upgrade package for version 24.0.0
- Follow the on-screen upgrade wizard instructions
- Restart the WhatsUp Gold services after the upgrade completes
- Verify the installation by logging into the web interface
- Confirm the version number reflects 24.0.0 or later in the About section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6672 — 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-6672 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