dbcve.org
Whatsup GoldApplication · Progress

CVE-2023-6365

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 device group.   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 · high confidence

A stored cross-site scripting (XSS) vulnerability exists in WhatsUp Gold versions prior to 2023.1. An attacker can inject malicious JavaScript payloads into a device group field. When authenticated users interact with the compromised device group in the web interface, the payload executes within their browser session.

MitigationUpgrade WhatsUp Gold to version 2023.1 or later to receive the security patch. Alternatively, restrict administrative access to device group configuration and monitor for suspicious device group entries.

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
    Look for WhatsUp Gold installation directory, typically in C:\Program Files\Progress\WhatsUp Gold or check Windows Programs and Features for Progress WhatsUp Gold entry
    Affected if WhatsUp Gold is present on the system
  2. Determine installed WhatsUp Gold version
    Check the installed version through Windows Programs and Features, or look for version info in the WhatsUp Gold installation directory, or access the web interface and check the About/Help section
    Affected if Installed version is lower than 23.1.0 (for example, 23.0.x, 22.x, or earlier)
  3. Verify web interface is accessible
    Confirm the WhatsUp Gold web interface is reachable at the configured URL (typically https://hostname or http://hostname)
    Affected if Web interface is accessible and version is below 23.1.0
  4. Inspect device group fields for XSS payloads
    Navigate to Device Groups in the web interface and examine the Group Name and Description fields for any unexpected script tags, JavaScript event handlers, or encoded payloads. Review the HTML source of these pages using browser developer tools if needed
    Affected if Any device group contains malicious JavaScript payloads in its name, description, or custom fields

You are affected if WhatsUp Gold version is below 23.1.0 AND the web interface is accessible AND malicious scripts are found in device group configuration fields.

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

Upgrade WhatsUp Gold to version 2023.1 or later to receive the security patch. Alternatively, restrict administrative access to device group configuration and monitor for suspicious device group entries.

Recommended fix Moderate confidence

WhatsUp Gold 23.1.0 (2023.1)

  1. Navigate to the Progress WhatsUp Gold download page or access the customer portal at www.progress.com
  2. Locate WhatsUp Gold version 23.1.0 (also referred to as 2023.1)
  3. Download the installer for your platform
  4. Backup your current WhatsUp Gold configuration and database
  5. Stop the WhatsUp Gold services
  6. Run the installer to upgrade to version 23.1.0
  7. Follow the installation wizard prompts
  8. Start the WhatsUp Gold services after installation completes

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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