dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5010

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
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 vulnerability exists in the TestController functionality.  A specially crafted unauthenticated HTTP request can lead to a disclosure of sensitive information.

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 · moderate confidence

WhatsUp Gold versions before 2023.1.3 contain an information disclosure vulnerability in the TestController component. An unauthenticated attacker can send specially crafted HTTP requests to the TestController functionality and obtain sensitive information without any authentication credentials.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later to remediate this vulnerability. If immediate patching is not feasible, implement network segmentation to restrict unauthorized access to the TestController endpoint.

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. Check WhatsUp Gold installed version
    Open the WhatsUp Gold web interface and navigate to Help > About, or check the installation directory for version information files. Alternatively, check the Windows Programs and Features list.
    Affected if The installed version is lower than 23.1.3 (any version before 23.1.3 is affected)
  2. Identify TestController endpoint accessibility
    Check if the /TestController or similar endpoint is exposed in the IIS/web server configuration for WhatsUp Gold. Review the web application's routing configuration or proxy settings.
    Affected if The TestController endpoint is reachable without authentication (the vulnerability requires this endpoint to be accessible)
  3. Verify network exposure of WhatsUp Gold web interface
    Review firewall rules and network ACLs to determine if the WhatsUp Gold web interface (typically ports 80/443 or custom configured ports) is exposed to untrusted networks or the internet.
    Affected if The interface is accessible from untrusted networks without VPN or authentication barriers
  4. Check for recent unauthorized access indicators
    Review IIS/web server logs for unusual requests to /TestController endpoints, especially from external IP addresses or in high volumes.
    Affected if There are log entries showing unauthenticated requests to TestController paths from untrusted sources

You are affected if WhatsUp Gold version is below 23.1.3 AND the TestController endpoint is accessible to unauthenticated users on your network.

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. If immediate patching is not feasible, implement network segmentation to restrict unauthorized access to the TestController endpoint.

Recommended fix Moderate confidence

WhatsUp Gold 23.1.3 or latest stable release

  1. Back up the current WhatsUp Gold installation and database before proceeding with any upgrade
  2. Navigate to the Progress WhatsUp Gold download page or contact Progress support to obtain version 23.1.3 or later
  3. Download the WhatsUp Gold 23.1.3 (or latest available) upgrade package
  4. Stop all WhatsUp Gold services before applying the upgrade
  5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. Restart WhatsUp Gold services after the upgrade completes
  7. Verify that the TestController functionality is now properly secured and the vulnerability is mitigated
  8. Confirm that all monitoring and alerting functions are operating normally post-upgrade
Caveat Review the 23.1.3 release notes for any configuration or feature changes that may require adjustment; 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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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