dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5015

HIGH · 8.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 authenticated SSRF vulnerability in Wug.UI.Areas.Wug.Controllers.SessionControler.Update allows a low privileged user to chain this SSRF with an Improper Access Control vulnerability. This can be used to escalate privileges to Admin.

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

An authenticated Server-Side Request Forgery (SSRF) vulnerability in the SessionController.Update endpoint of WhatsUp Gold allows a low-privileged authenticated user to make the application server perform arbitrary HTTP requests. This SSRF can be chained with an Improper Access Control flaw, enabling privilege escalation from a standard user to Administrator privileges.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later to obtain the vendor-supplied patch that addresses both the SSRF and improper access control vulnerabilities.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WhatsUp Gold is installed
    Check for the WhatsUp Gold installation directory (typically C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold), or look for the 'WhatsUp Gold' Windows service in Services.msc
    Affected if WhatsUp Gold is installed on the system
  2. Determine the installed WhatsUp Gold version
    Check the version by reviewing the file properties of the main executable (usually wugmanager.exe or nmwucore.dll) in the installation directory, or check the WhatsUp Gold web interface version information typically found in the Help > About page
    Affected if The installed version is earlier than 23.1.3 (any version < 23.1.3 is affected)
  3. Verify the SessionController.Update endpoint exists
    Inspect the application web logs or configuration to confirm the SessionController.Update endpoint is present and accessible in the WhatsUp Gold web application (typically under /api/session or similar authentication-related paths)
    Affected if The SessionController.Update endpoint is present and exposed via the web interface
  4. Check for low-privileged user accounts
    Review user accounts in WhatsUp Gold administration (Users and Roles section) to identify non-administrator accounts that could potentially exploit this vulnerability
    Affected if There are authenticated non-administrator users in the system who have API access

A system is affected if it runs WhatsUp Gold version earlier than 23.1.3 with the SessionController.Update endpoint exposed and low-privileged user accounts present.

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 obtain the vendor-supplied patch that addresses both the SSRF and improper access control vulnerabilities.

Recommended fix High confidence

WhatsUp Gold 23.1.3 or later

  1. 1. Verify current WhatsUp Gold version by checking the Help > About section in the application
  2. 2. If version is below 23.1.3, plan for upgrade during a maintenance window
  3. 3. Download WhatsUp Gold version 23.1.3 or later from the Progress Customer Portal (www.progress.com/customerzone)
  4. 4. Back up the current WhatsUp Gold configuration and database
  5. 5. Stop all WhatsUp Gold services before upgrading
  6. 6. Run the installer for the new version
  7. 7. Follow the installation wizard prompts to complete the upgrade
  8. 8. Start WhatsUp Gold services after installation completes
Caveat Review release notes for any configuration changes or feature modifications between your current version and 23.1.3

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

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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