dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5018

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 Path Traversal vulnerability exists Wug.UI.Areas.Wug.Controllers.SessionController.LoadNMScript. This allows allows reading of any file from the applications web-root directory .

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 path traversal vulnerability in WhatsUp Gold's SessionController.LoadNMScript method allows remote attackers to read arbitrary files within the web-root directory without authentication. The lack of proper input validation on file path parameters enables attackers to traverse directories using '../' sequences.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later. If immediate patching is not feasible, implement web application firewall rules to block path traversal patterns and restrict file access permissions on the web 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
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. Identify if WhatsUp Gold is installed
    Look for WhatsUp Gold installation on the system. Check common locations such as C:\Program Files\Progress\WhatsUp or C:\Program Files (x86)\Progress\WhatsUp. Inspect Program Files for the 'Progress' folder containing WhatsUp Gold.
    Affected if WhatsUp Gold is found installed on the system
  2. Determine the installed WhatsUp Gold version
    Locate version information in the installation directory, typically in an About or Version file, or check the Windows Programs and Features list for the installed version. The version format appears as year.release such as 23.1.x.
    Affected if The installed version is lower than 23.1.3
  3. Confirm the web application is running
    Check if the WhatsUp Gold web interface is active. This is typically accessible on port 80 or 443, or configured ports during installation. Use netstat or check Windows Services to verify the web service is running.
    Affected if The WhatsUp Gold web service is running and accessible
  4. Verify the SessionController endpoint is exposed
    Attempt to access the SessionController.LoadNMScript endpoint via the web interface. The endpoint is typically reachable at a path containing 'SessionController' or 'LoadNMScript'. Check if the application responds to requests at this controller path.
    Affected if The SessionController.LoadNMScript method is accessible without authentication

A system is affected if WhatsUp Gold version lower than 23.1.3 is installed and the web interface with the vulnerable SessionController endpoint 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. If immediate patching is not feasible, implement web application firewall rules to block path traversal patterns and restrict file access permissions on the web server.

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) or their authorized distribution channels
  2. Review the upgrade guide and release notes for WhatsUp Gold 23.1.3
  3. Backup your current WhatsUp Gold installation, including the database and configuration files
  4. Ensure you have valid licenses and credentials for the upgrade
  5. Run the installer for the new version, following the on-screen prompts
  6. After installation, verify that the web interface is accessible and all services are running
  7. Confirm the vulnerability is remediated by testing that the path traversal in SessionController.LoadNMScript is no longer exploitable
Caveat Review release notes for potential configuration changes or migration requirements between versions; test in a 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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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