CVE-2024-12108
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 · uneditedIn WhatsUp Gold versions released before 2024.0.2, an attacker can gain access to the WhatsUp Gold server via the public API.
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 confidenceCritical pre-authentication vulnerability in WhatsUp Gold's public API allows unauthenticated attackers to gain direct access to the WhatsUp Gold server. The vulnerability affects all versions prior to 2024.0.2 and is exploitable without any user interaction or credentials.
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>= 23.1.0, < 24.0.2CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed WhatsUp Gold versionCheck the WhatsUp Gold GUI version info (Help > About) or locate the installation directory and look for version metadata in application files or logsAffected if Installed version is 23.1.0 or higher but lower than 24.0.2
-
Verify WhatsUp Gold web interface accessibilityConfirm the WhatsUp Gold web application is accessible by accessing the login page via browser (typically http or https on port 80/443 or configured ports)Affected if The web interface is reachable from network locations where untrusted users could connect
-
Determine if API endpoints are publicly exposedTest access to common WhatsUp Gold API paths such as /api/ or the public API endpoint from an untrusted network location or verify firewall/network ACLs permit external access to these pathsAffected if API endpoints are accessible from untrusted/external networks without network segmentation or firewall restrictions
-
Confirm vulnerability is exploitable without authenticationNote that this CVE allows unauthenticated access - if the API is exposed and version is in affected range, exploitation is possible without valid credentialsAffected if API is exposed and version falls within 23.1.0 to 24.0.1 range
User is affected if WhatsUp Gold version is 23.1.0 or higher but lower than 24.0.2 AND the public API is network-accessible from untrusted locations.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.0.2
Upgrade WhatsUp Gold to version 2024.0.2 or later to remediate this vulnerability. Until patched, restrict public access to the WhatsUp Gold API endpoints using network segmentation or firewall rules.
WhatsUp Gold 24.0.2
- Download WhatsUp Gold version 24.0.2 or later from the Progress website (www.progress.com/products/whatsup-gold)
- Ensure you have a complete backup of your WhatsUp Gold installation and database before upgrading
- Review the upgrade documentation provided by Progress for WhatsUp Gold 24.0.2
- Execute the upgrade installer on the WhatsUp Gold server
- Verify the upgrade was successful by logging into the WhatsUp Gold web interface
- Confirm that the public API endpoint now requires proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-12108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12108 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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