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 24 Mar 2025.
Whatsup GoldApplication · Progress

CVE-2024-4885

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 2023.1.3, an unauthenticated Remote Code Execution vulnerability in Progress WhatsUpGold.  The WhatsUp.ExportUtilities.Export.GetFileWithoutZip allows execution of commands 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 Remote Code Execution vulnerability in Progress WhatsUp Gold versions before 2023.1.3 exists in the WhatsUp.ExportUtilities.Export.GetFileWithoutZip function. This allows remote attackers to execute arbitrary commands with iisapppool\nmconsole (IIS app pool) privileges without any authentication.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later to obtain the vendor patch. Until patched, restrict network access to the WhatsUp Gold web interface to trusted sources only.

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
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 installation path
    Locate the WhatsUp Gold installation directory, typically found in C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold
    Affected if The application is installed in any directory
  2. Determine installed WhatsUp Gold version
    Check the version of the installed WhatsUp Gold application. Look for version information in the web interface (typically accessible at http://localhost/NmConsole/ or https://localhost/NmConsole/), check the Windows Programs and Features list, or examine version.dll or other binaries in the installation directory
    Affected if The installed version is lower than 23.1.3 (for example, 23.1.0, 22.1.0, 21.0.x, or earlier)
  3. Verify the Export module is accessible
    Confirm the WhatsUp Gold web interface is accessible and the Export functionality is present. The vulnerable endpoint is typically at /NmConsole/Export/
    Affected if The web interface is accessible and the Export module is enabled
  4. Confirm IIS application pool identity
    Check the IIS application pool running WhatsUp Gold (typically NmConsole or nmconsole). In IIS Manager, select Application Pools, find the relevant pool, and view its Advanced Settings to see the Identity (usually IIS AppPool\nmconsole or IIS AppPool\nmconsole)
    Affected if The application pool is running under a privileged account (note: the vulnerability runs with iisapppool\nmconsole privileges regardless of identity setting)

You are affected if your installed WhatsUp Gold version is below 23.1.3 and the web-based Export functionality is accessible.

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 patch. Until patched, restrict network access to the WhatsUp Gold web interface to trusted sources only.

Recommended fix Moderate confidence

WhatsUp Gold 23.1.3 or later

  1. Download WhatsUp Gold version 23.1.3 or later from the official Progress website (www.progress.com)
  2. Backup the current WhatsUp Gold installation and database before upgrading
  3. Stop the WhatsUp Gold services and IIS application pools
  4. Install the new version following the standard upgrade procedure
  5. Restart the WhatsUp Gold services and IIS application pools
  6. Verify the installation by logging into the WhatsUp Gold web interface
  7. Confirm that the WhatsUp.ExportUtilities.Export.GetFileWithoutZip vulnerability is no longer accessible

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

Fix this in Whatsup Gold Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
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,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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