CVE-2023-6367
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 Roles. 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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in WhatsUp Gold versions before 2023.1. An attacker can craft a malicious XSS payload and store it within the Roles functionality of the application. When other WhatsUp Gold users interact with these compromised role entries, the embedded JavaScript executes in their browsers within the application's context.
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 versionLog into the WhatsUp Gold web interface and navigate to the Help or About section, typically found in the main menu. Alternatively, check the installation directory for version information or consult system documentation.Affected if The installed version is any release before 23.1.0 (versions 23.0.x, 22.x, 21.x, etc.)
-
Confirm Roles functionality is presentVerify that the Roles management interface is accessible in the WhatsUp Gold application. Navigate to the administrative or configuration section where user roles and permissions are defined.Affected if The Roles feature exists and is available in the installation, regardless of whether you have administrative access to modify it
-
Review Roles for suspicious contentAccess the Roles configuration panel and examine all existing role entries for any unexpected or encoded characters that may indicate injected script tags (such as <script>, javascript:, onload, onerror, or similar event handlers).Affected if Any role entry contains JavaScript code, HTML tags, or unusual characters that were not intentionally configured by your administrators
You are affected if your WhatsUp Gold installation is version 23.0.x or earlier and contains unexpected script content in the Roles configuration that could execute when users view those roles.
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 2023.1 or later to obtain the vendor patch. If immediate upgrading is not feasible, implement output encoding and input validation on all Role-related fields and consider deploying Content Security Policy (CSP) headers as a defense-in-depth measure.
WhatsUp Gold 23.1.0
- 1. Create a complete backup of the current WhatsUp Gold installation, including the database and configuration files.
- 2. Stop all WhatsUp Gold services (using the Services console or nmx command line utility).
- 3. Download WhatsUp Gold version 23.1.0 from the official Progress website (www.progress.com) or the Progress Community portal.
- 4. Run the installer for version 23.1.0 and follow the upgrade wizard prompts.
- 5. When prompted, point the installer to the existing database to preserve current configurations and monitoring data.
- 6. Complete the installation and restart all WhatsUp Gold services.
- 7. Log in to the WhatsUp Gold web interface and verify that all features, particularly the Roles functionality, are working correctly.
- 8. Confirm the upgrade by navigating to Help > About and verifying the version number displays 23.1.0.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6367 — 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-6367 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