dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-4883

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
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, a Remote Code Execution issue exists in Progress WhatsUp Gold. This vulnerability allows an unauthenticated attacker to achieve the RCE as a service account through NmApi.exe.

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 exists in Progress WhatsUp Gold's NmApi.exe component in versions prior to 2023.1.3. An attacker can execute arbitrary code as the service account running the WhatsUp Gold application without any authentication credentials.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later to address this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure to the NmApi.exe interface.

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 location
    Look for the WhatsUp Gold installation directory, typically under C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold. Check Windows Services to confirm the service is installed.
    Affected if WhatsUp Gold is installed on the system
  2. Determine installed WhatsUp Gold version
    Locate the NmApi.exe file within the WhatsUp Gold installation directory (commonly in the subfolder containing API components). Right-click the file, select Properties, and check the Version tab. Alternatively, check the WhatsUp Gold web interface footer for the version number or check the registry under HKLM\SOFTWARE\Progress\WhatsUp Gold for the version key.
    Affected if The version shown is earlier than 23.1.3 (for example, 23.1.0, 22.1.x, or older)
  3. Verify NmApi.exe component exists
    Navigate to the WhatsUp Gold installation directory and search for NmApi.exe. This is the vulnerable component. Confirm the file exists in the NmApi or corresponding API folder.
    Affected if NmApi.exe exists in the installation directory
  4. Check NmApi network exposure
    Review firewall rules and network configuration to determine if the NmApi interface is accessible from network segments outside the trusted environment. Check if port 47443 (typical WhatsUp Gold API port) or the configured API port is open to untrusted networks.
    Affected if The NmApi interface is exposed to untrusted networks or the internet without proper network segmentation

You are affected if WhatsUp Gold is installed with a version earlier than 23.1.3 and the NmApi.exe component is present and network-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 address this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure to the NmApi.exe interface.

Recommended fix High confidence

WhatsUp Gold 23.1.3 or later

  1. Verify the current WhatsUp Gold version by checking the NmApi.exe file properties or the WhatsUp Gold console About section
  2. Download WhatsUp Gold version 23.1.3 or later from the official Progress website (www.progress.com) or authorized distribution channels
  3. Review the WhatsUp Gold upgrade documentation for version 23.1.3
  4. Create a full backup of the WhatsUp Gold database and configuration files before proceeding
  5. Stop all WhatsUp Gold services to ensure a clean upgrade process
  6. Run the installer for version 23.1.3 with appropriate administrative privileges
  7. Follow the on-screen upgrade wizard prompts, selecting the upgrade option
  8. After installation completes, verify that NmApi.exe has been updated to the patched version
Caveat Review release notes for version 23.1.3 to check for any configuration or feature changes that may require adjustment; test in non-production environment first

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-4883 — 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-4883 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