dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-12105

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 24.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 2024.0.2, an authenticated user can use a specially crafted HTTP request that can lead to information disclosure.

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

In WhatsUp Gold versions released before 2024.0.2, an authenticated user can send a specially crafted HTTP request to trigger information disclosure. The vulnerability requires valid authentication credentials but allows the attacker to access sensitive data through malformed HTTP parameters or endpoints.

MitigationUpgrade WhatsUp Gold to version 2024.0.2 or later. Additionally, enforce least-privilege access controls for authenticated users and monitor HTTP traffic for anomalous request patterns indicative of exploitation.

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.0, < 24.0.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine installed WhatsUp Gold version
    Open the WhatsUp Gold web interface and check the version displayed in the About section, or check the installation directory for a version file. You can also check the Windows Programs and Features list.
    Affected if The version is 23.1.0 or higher but lower than 24.0.2.
  2. Verify the WhatsUp Gold web interface is accessible
    Attempt to reach the WhatsUp Gold login page via HTTP or HTTPS from a client system. Check if ports 80, 443, or the configured web service ports are listening and responding.
    Affected if The web interface is exposed and reachable from your detection point.
  3. Review enabled user accounts
    Check the WhatsUp Gold user management console or Active Directory integration settings to list all accounts with valid login credentials for the application.
    Affected if There are active user accounts configured, especially those with elevated or standard privileges.
  4. Inspect HTTP access logs for anomalous requests
    Locate and review the WhatsUp Gold IIS or web server access logs, looking for requests with unusual parameters, unexpected endpoints, or patterns that deviate from normal user behavior.
    Affected if You find requests containing malformed parameters, unexpected endpoint access, or high-frequency requests from authenticated sessions accessing sensitive data paths.

You are affected if your WhatsUp Gold installation version falls within 23.1.0 through 24.0.1 and the web interface is accessible with valid user accounts present.

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 24.0.2 or later
Fixed in 24.0.2
Interim mitigation

Upgrade WhatsUp Gold to version 2024.0.2 or later. Additionally, enforce least-privilege access controls for authenticated users and monitor HTTP traffic for anomalous request patterns indicative of exploitation.

Recommended fix Moderate confidence

WhatsUp Gold 24.0.2 or later

  1. 1. Backup the current WhatsUp Gold configuration and database before starting the upgrade process.
  2. 2. Download WhatsUp Gold version 24.0.2 or later from the Progress official download portal.
  3. 3. Stop the WhatsUp Gold services to ensure a clean upgrade.
  4. 4. Run the installer for the new version, following the on-screen upgrade instructions.
  5. 5. After installation completes, verify the upgrade by checking the WhatsUp Gold version in the web interface (Help > About).
  6. 6. Test that the application functions normally and verify the path traversal vulnerability is no longer present.
  7. 7. Restart the WhatsUp Gold services if they did not start automatically.
Caveat Review release notes for any configuration or feature changes between 23.x and 24.x versions before upgrading

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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