CVE-2023-6366
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 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 Alert Center. 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in WhatsUp Gold's Alert Center for versions prior to 2023.1. Attackers can inject malicious JavaScript payloads into the Alert Center, which persist and execute when legitimate users view or interact with the crafted alert content in their browsers.
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.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed WhatsUp Gold versionLocate the WhatsUp Gold installation and check the version information, typically found in the application itself under Help > About, or in the installation directory's version metadata. Compare your version number to the affected range (versions prior to 23.1.0).Affected if The installed version is lower than 23.1.0 (or 2023.1)
-
Confirm Alert Center module is activeAccess the WhatsUp Gold web interface and navigate to the Alert Center section to verify the module is enabled and accessible to users.Affected if Alert Center is accessible and in use within your environment
-
Inspect existing alerts for suspicious contentWithin the Alert Center interface, review all configured alerts and examine the alert fields (name, description, message body) for any unusual JavaScript tags, event handlers (onerror, onload, onclick), or encoded payloads that may indicate injection.Affected if Any alert contains unescaped HTML/JavaScript syntax or known malicious XSS patterns
-
Check user browser console for XSS errorsLog in as a standard user, navigate to the Alert Center, and open the browser developer console (F12). Look for any JavaScript execution errors or injected script behavior when viewing alert details.Affected if JavaScript executes unexpectedly or console shows XSS-related errors when viewing alerts
You are affected if running WhatsUp Gold version below 23.1.0 and the Alert Center module is accessible, as attackers could have injected malicious scripts that execute when users view alerts.
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 · scoped23.1.0
Upgrade to WhatsUp Gold version 2023.1 or later. Additionally, implement robust input validation and output encoding on all Alert Center data fields to prevent XSS injection.
WhatsUp Gold 23.1.0 (2023.1)
- Obtain WhatsUp Gold version 23.1.0 or later from the official Progress website (www.progress.com) or their authorized download portal
- Review the WhatsUp Gold upgrade documentation for version 23.1.0
- Back up your current WhatsUp Gold configuration and database before proceeding with the upgrade
- Execute the upgrade installer for version 23.1.0 following the standard upgrade procedure
- After upgrade completion, verify that the Alert Center functionality is working correctly
- Confirm the installed version is 23.1.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6366 — 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-2023-6366 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