dbcve.org
Whatsup GoldApplication · Progress

CVE-2024-5008

HIGH · 8.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 23.1.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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 2023.1.3, an authenticated user with certain permissions can upload an arbitrary file and obtain RCE using Apm.UI.Areas.APM.Controllers.Api.Applications.AppProfileImportController.

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 authenticated user with specific permissions can upload arbitrary files through the AppProfileImportController in WhatsUp Gold versions before 2023.1.3, leading to remote code execution. The vulnerability stems from insufficient validation of uploaded files in the APM import functionality.

MitigationUpgrade WhatsUp Gold to version 2023.1.3 or later. Additionally, review and restrict user permissions for the APM module to minimize the attack surface until the upgrade is completed.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed WhatsUp Gold version
    Locate the WhatsUp Gold installation and determine the exact version number. This is typically visible in the product UI (Help > About) or in installation files. Compare your version against the affected range: versions prior to 23.1.3 are vulnerable.
    Affected if Your installed version is earlier than 23.1.3 (for example, 23.1.0, 22.x, 21.x)
  2. Verify if APM module is accessible
    Determine whether the Application Performance Monitoring (APM) module is enabled and accessible in your WhatsUp Gold instance. Check user role permissions to see if the APM functionality is available to your account.
    Affected if The APM module is enabled and you have an authenticated user account with APM permissions
  3. Confirm APM import feature is available
    In the WhatsUp Gold interface, navigate to the APM section and determine whether the import functionality (AppProfileImportController) is present and accessible. This is typically found under APM settings or configuration.
    Affected if The APM import feature is accessible to your authenticated user account
  4. Review user account permissions
    Examine the specific permissions assigned to your user account, particularly any permissions related to file uploads, APM configuration, or import functionality. Check if the account has elevated privileges that would allow using the import controller.
    Affected if Your authenticated account has permissions to access the file import functionality in the APM module

You are affected if your WhatsUp Gold version is earlier than 23.1.3 AND you have an authenticated user with APM module import permissions who can access the AppProfileImportController.

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. Additionally, review and restrict user permissions for the APM module to minimize the attack surface until the upgrade is completed.

Recommended fix Moderate confidence

WhatsUp Gold 23.1.3 or later

  1. 1. Ensure you have a complete backup of your WhatsUp Gold installation and database.
  2. 2. Download WhatsUp Gold version 23.1.3 or later from the official Progress website (www.progress.com) or their authorized distribution channels.
  3. 3. Before applying the update, review the release notes for any specific upgrade prerequisites or注意事项.
  4. 4. Test the upgrade in a non-production environment first to verify functionality.
  5. 5. Apply the upgrade to your production environment following standard change management procedures.
  6. 6. Verify that the AppProfileImportController vulnerability is no longer exploitable after the upgrade.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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