dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5009

HIGH · 8.4 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
89/100
Remediation priority · High
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 2023.1.3, an Improper Access Control vulnerability in Wug.UI.Controllers.InstallController.SetAdminPassword allows local attackers to modify admin'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 confidence

Improper Access Control vulnerability in Wug.UI.Controllers.InstallController.SetAdminPassword in WhatsUp Gold versions before 2023.1.3 allows local attackers to modify the administrator password without authentication, potentially gaining full administrative access to the application and underlying system.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later to remediate this vulnerability. Since this is a local attack vector, ensure proper system access controls and limit physical and terminal access to the server.

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.3

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Verify WhatsUp Gold is installed
    Check for WhatsUp Gold installation by looking for its program directory (typically C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold) or check Windows Programs and Features for 'Progress WhatsUp Gold' entry
    Affected if WhatsUp Gold is found on the system
  2. Determine installed WhatsUp Gold version
    Check the version by opening the WhatsUp Gold console and looking at the About/Help section, or locate the NuGet packages.config or assembly version within the installation directory, or check the Windows Registry under HKLM\SOFTWARE\Progress\WhatsUp Gold for the Version value
    Affected if Version cannot be determined or is lower than 23.1.3
  3. Compare version against affected range
    Compare your installed version number to 23.1.3 - any version below 23.1.3 (including 23.1.0, 23.0.x, 22.x, 21.x, and earlier) is within the affected range
    Affected if Installed version is less than 23.1.3
  4. Confirm local attack vector exposure
    Since this is a local vulnerability requiring physical or terminal access to the WhatsUp Gold server, assess whether untrusted users have local access to the server where WhatsUp Gold is hosted
    Affected if Untrusted or unauthorized local users have access to the WhatsUp Gold server

You are affected if WhatsUp Gold is installed with a version lower than 23.1.3 and the server is accessible to untrusted local users.

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 23.1.3 or later
Fixed in 23.1.3
Interim mitigation

Upgrade WhatsUp Gold to version 2023.1.3 or later to remediate this vulnerability. Since this is a local attack vector, ensure proper system access controls and limit physical and terminal access to the server.

Recommended fix High confidence

WhatsUp Gold 23.1.3 or later

  1. 1. Identify the current WhatsUp Gold version by checking the application or system information.
  2. 2. Navigate to the official Progress website (www.progress.com) or the Progress Community (community.progress.com) to download WhatsUp Gold version 23.1.3 or later.
  3. 3. Before upgrading, back up the current WhatsUp Gold configuration and database to prevent data loss.
  4. 4. Install the updated WhatsUp Gold version 23.1.3 or the latest available release, following the standard installation procedures.
  5. 5. After installation, verify that the SetAdminPassword endpoint in Wug.UI.Controllers.InstallController has been properly secured.
  6. 6. Confirm that the admin password can no longer be modified by unauthorized local users.

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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 locally
dbcve dependency scanner

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