dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5019

HIGH · 7.5 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
84/100
Remediation priority · High
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 2023.1.3,  an unauthenticated Arbitrary File Read issue exists in Wug.UI.Areas.Wug.Controllers.SessionController.CachedCSS. This vulnerability allows reading of any file with iisapppool\NmConsole privileges.

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 unauthenticated arbitrary file read vulnerability exists in WhatsUp Gold's SessionController.CachedCSS endpoint, allowing remote attackers to read any file accessible to the iisapppool\NmConsole service account without authentication.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later to remediate this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm WhatsUp Gold installation
    Check for WhatsUp Gold installation directory at typical paths: C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold. Also check Windows Services for 'WhatsUp Gold' service.
    Affected if WhatsUp Gold is installed and the service is running
  2. Identify installed version
    Check the version by examining the NmConsole.exe file properties in the installation directory, or look in Windows Registry at HKLM\SOFTWARE\Progress\WhatsUp\Setup\Version
    Affected if Installed version is below 23.1.3 (check if version starts with 23.1.0, 23.0.x, 22.x, or earlier)
  3. Verify SessionController endpoint exposure
    Attempt to access the vulnerable endpoint locally or remotely: http(s)://<target>/NmConsole/SessionController/CachedCSS?file=../../../../windows/win.ini (note: this is a test path, do not actually exploit). Check if the application responds to requests on port 443 or 80.
    Affected if The NmConsole web application is accessible and responds to requests on standard HTTP/HTTPS ports
  4. Check service account file access
    Verify the service account iisapppool\NmConsole has access to sensitive files by reviewing NTFS permissions on critical system files (C:\Windows\System32\config\SAM, C:\Windows\win.ini) that would be readable if the vulnerability were exploited.
    Affected if The NmConsole service account has broad file system permissions that would allow reading sensitive system files

Environment is affected if WhatsUp Gold version 23.1.3 or higher is not installed AND the NmConsole web interface is network-accessible, allowing unauthenticated attackers to read files via the SessionController.CachedCSS endpoint.

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.

Recommended fix High confidence

WhatsUp Gold 23.1.3 or later

  1. Backup the WhatsUp Gold database and configuration files
  2. Download WhatsUp Gold version 23.1.3 or later from the official Progress website (www.progress.com or community.progress.com)
  3. Stop the WhatsUp Gold services and IIS
  4. Run the installer to upgrade the existing installation
  5. Start the WhatsUp Gold services and verify the application is running
  6. Test that the CachedCSS endpoint no longer allows arbitrary file access

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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