dbcve.org
Whatsup GoldApplication · Progress

CVE-2023-6364

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 23.1.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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, a stored cross-site scripting (XSS) vulnerability has been identified.  It is possible for an attacker to craft a XSS payload and store that value within a dashboard component.   If a WhatsUp Gold user interacts with the crafted payload, the attacker would be able to execute malicious JavaScript within the context of the victims browser.

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

This is a stored cross-site scripting (XSS) vulnerability in WhatsUp Gold where an attacker can inject malicious JavaScript payloads into dashboard components. When legitimate users view or interact with the compromised dashboard, the stored payload executes in their browser context, potentially allowing session hijacking, data theft, or actions on behalf of the user.

MitigationApply proper input validation and output encoding/sanitization on all dashboard component inputs to neutralize malicious scripts before storage and before rendering. Upgrade to WhatsUp Gold version 2023.1 or later.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 WhatsUp Gold installation and version
    Locate the WhatsUp Gold installation directory and check the product version, typically found in the application UI under Help > About or in installation metadata files
    Affected if The installed version is below 23.1.0
  2. Compare installed version to vulnerability threshold
    Review the identified version number against the affected range: any version prior to 23.1.0 is vulnerable
    Affected if Version is lower than 23.1.0
  3. Inspect dashboard component configurations
    Access the WhatsUp Gold admin console and review dashboard widget/component configurations for any unexpected script tags, event handlers, or JavaScript URLs in text fields
    Affected if Malicious JavaScript payloads are present in stored dashboard configurations
  4. Audit recent dashboard modifications
    Check dashboard change logs or audit trails for unexpected modifications to dashboard components, particularly those containing script elements
    Affected if Recent changes introduced unsanitized script content into dashboard components

You are affected if WhatsUp Gold version is below 23.1.0 AND your dashboards contain unsanitized script content that could execute in user browsers.

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.0 or later
Fixed in 23.1.0
Interim mitigation

Apply proper input validation and output encoding/sanitization on all dashboard component inputs to neutralize malicious scripts before storage and before rendering. Upgrade to WhatsUp Gold version 2023.1 or later.

Recommended fix Moderate confidence

WhatsUp Gold 23.1.0 (2023.1)

  1. Download WhatsUp Gold version 23.1.0 or later from the official Progress website (www.progress.com)
  2. Back up the current WhatsUp Gold installation and database
  3. Stop the WhatsUp Gold services
  4. Install/upgrade to WhatsUp Gold 23.1.0
  5. Start the WhatsUp Gold services
  6. Verify the upgrade was successful by checking the version number in the About section
Caveat Review release notes for any configuration changes required when upgrading to 23.1.0

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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