dbcve.org
Wyse Management SuiteApplication · Dell

CVE-2026-22765

HIGH · 8.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 5.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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.5, contain a Missing Authorization vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Elevation of Privileges.

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.5 contain a Missing Authorization vulnerability allowing a low-privileged remote attacker to bypass access controls and elevate privileges to higher permission levels within the application.

MitigationUpgrade to WMS 5.5 or later which contains the proper authorization controls. If immediate patching is not possible, restrict network access to trusted users and monitor for unauthorized privilege escalation attempts.

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.5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 if Dell Wyse Management Suite is installed
    Locate the WMS installation directory or check running services for WMS components. Common paths include C:\Program Files\Dell\Wyse\ManagementSuite or /opt/wyse/managementsuite on Linux.
    Affected if WMS is not found on the system, then this CVE does not apply.
  2. Determine the installed WMS version
    Access the WMS admin console and navigate to Help > About, or check the version file in the installation directory (typically version.txt or similar). Alternatively, check the installed packages via system package manager if installed via Linux packages.
    Affected if The version displayed is less than 5.5 (for example, 5.4.x, 5.3.x, or earlier), then the system is vulnerable to this missing authorization flaw.
  3. Verify WMS web interface accessibility
    Confirm the WMS web interface is reachable by accessing the management console URL (typically https://hostname:8443 or similar port). Check if the application is listening on network interfaces.
    Affected if The WMS web interface is exposed and the installed version is below 5.5, an unauthenticated or low-privileged attacker could potentially exploit the authorization bypass.
  4. Review user account configurations
    In the WMS admin console, navigate to Administration > Users or similar user management section. Identify if low-privileged user accounts exist with limited permissions.
    Affected if Low-privileged accounts exist and the WMS version is below 5.5, these accounts could be leveraged for privilege escalation via the missing authorization vulnerability.

The environment is affected if Dell Wyse Management Suite is installed and the running version is any release prior to version 5.5.

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.5 or later
Fixed in 5.5
Interim mitigation

Upgrade to WMS 5.5 or later which contains the proper authorization controls. If immediate patching is not possible, restrict network access to trusted users and monitor for unauthorized privilege escalation attempts.

Recommended fix High confidence

Wyse Management Suite 5.5

  1. 1. Back up the current Wyse Management Suite database and configuration files
  2. 2. Review the WMS 5.5 release notes from Dell for any prerequisites or migration requirements
  3. 3. Download Wyse Management Suite version 5.5 or later from the Dell support portal
  4. 4. Stop all WMS services before upgrading
  5. 5. Run the WMS 5.5 installer on the WMS server
  6. 6. Follow the on-screen upgrade wizard instructions
  7. 7. After upgrade, verify all services start correctly
  8. 8. Test that low-privileged accounts can no longer escalate privileges
Caveat Check Dell release notes for WMS 5.5 - no specific breaking changes mentioned in provided description

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

Fix this in Wyse Management Suite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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