CVE-2025-36574
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 · uneditedDell Wyse Management Suite, versions prior to WMS 5.2, contain an Absolute Path Traversal vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information disclosure and Unauthorized access.
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 confidenceDell Wyse Management Suite versions prior to 5.2 contain an Absolute Path Traversal vulnerability. An unauthenticated remote attacker can exploit this by manipulating file path inputs to access sensitive files outside the intended directory, potentially disclosing configuration files, credentials, or other system information.
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< 5.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Dell Wyse Management Suite versionAccess the management console admin login page or check the software About/Version section within the web interface. Alternatively, check the installer or running service version through the system's installed programs list or service information.Affected if The displayed version number is lower than 5.2 (for example, 5.1.x, 5.0.x, or earlier releases)
-
Verify web management interface accessibilityConfirm the Dell Wyse Management Suite web interface is reachable on its configured port (typically 443 or 8443) by accessing the login URL from the management server itself or an authorized client.Affected if The web interface is exposed and responds to requests, indicating the vulnerable endpoint is network-accessible
-
Check for file path input functionalityLocate any file download, export, backup, or file access features within the management suite web interface that accept file path parameters.Affected if Features accepting file path parameters are present and accessible without authentication on the vulnerable version
-
Review access logs for path traversal attemptsExamine the Dell Wyse Management Suite server logs (typically found in the installation logs directory) for suspicious patterns such as '../' or absolute path requests in file access parameters.Affected if Log entries show path traversal patterns or unauthorized access to system directories outside the intended scope
Your environment is affected if Dell Wyse Management Suite version is detected as lower than 5.2 and the management web interface with file path input features is accessible over the network.
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 · scoped5.2
Upgrade to Dell Wyse Management Suite version 5.2 or later to obtain the vendor patch. If immediate upgrade is not possible, restrict network access to the management interface and implement input validation on file path parameters.
Wyse Management Suite 5.2
- Verify current Wyse Management Suite version by checking the WMS admin console or system information
- Schedule a maintenance window for the upgrade process
- Back up the current WMS configuration and database according to Dell backup procedures
- Download Wyse Management Suite version 5.2 from the Dell support website (support.dell.com)
- Follow Dell's official upgrade documentation to install WMS 5.2
- After upgrade, verify the installation was successful and the WMS services are running
- Confirm the vulnerability is remediated by reviewing system logs and verifying path traversal protections are in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36574 — 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-2025-36574 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