dbcve.org
Wyse Management SuiteApplication · Dell

CVE-2025-36577

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 5.2 or later.
See remediation →
65/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
Dell Wyse Management Suite, versions prior to WMS 5.2, contain an Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Script injection.

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

Dell Wyse Management Suite versions prior to 5.2 contain a cross-site scripting (XSS) vulnerability where user-supplied input is not properly neutralized during web page generation. An attacker with high privileges and remote access can inject malicious scripts into the application, which will be executed in the context of other users' sessions.

MitigationUpgrade to Dell Wyse Management Suite version 5.2 or later to obtain the vendor patch. Apply standard XSS mitigation practices such as input validation and output encoding as a temporary measure until the upgrade can be performed.

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
Wyse Management SuiteApplication
Affected:< 5.2

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/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 installed Dell Wyse Management Suite version
    Access the Wyse Management Suite admin console or check the software installation details. The version is typically displayed in the console header, about section, or can be retrieved via the management interface.
    Affected if The displayed version number is lower than 5.2 (for example, 5.1.x, 5.0.x, or earlier)
  2. Confirm web interface is enabled
    Verify that the Wyse Management Suite web interface is accessible by navigating to the management server URL using a web browser.
    Affected if The web interface is accessible and running, as this is the attack vector for the XSS vulnerability
  3. Identify privileged user accounts
    Review the user management section of the admin console to determine if accounts with high privileges (administrator-level access) exist in the system.
    Affected if High-privilege user accounts are present, as the CVE requires an attacker with high privileges to inject the malicious script
  4. Check for unusual script execution in the console
    Inspect browser developer console (F12) and network tab while using the web interface. Look for any injected scripts or unexpected behavior when viewing pages that accept user input.
    Affected if Unexpected script execution or console errors related to script injection are observed

A defender is affected if their Dell Wyse Management Suite installation version is lower than 5.2 and the web interface is accessible with high-privilege accounts in use.

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 5.2 or later
Fixed in 5.2
Interim mitigation

Upgrade to Dell Wyse Management Suite version 5.2 or later to obtain the vendor patch. Apply standard XSS mitigation practices such as input validation and output encoding as a temporary measure until the upgrade can be performed.

Recommended fix Moderate confidence

WMS 5.2

  1. 1. Back up the current Wyse Management Suite installation and database
  2. 2. Review the WMS 5.2 release notes and upgrade documentation from Dell support
  3. 3. Ensure the system meets the prerequisites for WMS 5.2 (check Dell compatibility guides)
  4. 4. Download Wyse Management Suite version 5.2 from Dell's official support website
  5. 5. Execute the upgrade following Dell's documented upgrade procedure
  6. 6. Verify the upgrade was successful by logging into the WMS console
  7. 7. Validate that the XSS vulnerability is no longer present
Caveat Review WMS 5.2 release notes for any configuration or feature changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wyse Management Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
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,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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