CVE-2022-46754
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 · uneditedWyse Management Suite 3.8 and below contain an improper access control vulnerability. A authenticated malicious admin user might access certain pro license features for which this admin is not authorized in order to configure user controlled external entities.
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 confidenceWyse Management Suite versions 3.8 and below have an improper access control vulnerability where authenticated admin users with limited privileges can bypass authorization checks to access pro license features they are not assigned. This allows a malicious admin to configure user-controlled external entities, representing a privilege escalation and authorization bypass issue.
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<= 3.8.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Wyse Management Suite versionAccess the Wyse Management Suite admin console and navigate to the About or System Information section to view the installed software version. Alternatively, check the installation directory or software inventory for the WMS version number.Affected if The installed version is 3.8.0 or any version below 3.8.0
-
Review admin user accounts and their assigned rolesIn the WMS admin console, navigate to the User Management or Administration section to list all admin users and their assigned privilege levels. Identify users who have limited or standard admin privileges rather than full administrator access.Affected if There are admin users with limited privileges (non-full-admin) configured in the system
-
Verify access to pro license features by non-pro usersUsing a test account with limited admin privileges (non-pro assigned), attempt to access or configure pro-license features such as user-controlled external entities, advanced reporting, or enterprise management functions. Check if the authorization check is enforced or bypassed.Affected if A limited-privilege admin user can access or configure pro-license features they were not assigned, indicating the authorization bypass is present
-
Examine audit logs for privilege escalation activityReview WMS audit logs or security logs for entries showing limited-privilege users accessing pro features, configuring external entities, or performing actions outside their assigned role scope.Affected if Audit logs show limited-privilege users accessing pro-license features or configuring settings typically restricted to higher privilege levels
The environment is affected if Wyse Management Suite version is 3.8.0 or below AND there are admin users with limited privileges who can access pro-license features they were not assigned, representing a successful authorization bypass.
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.
From vendor dataApply vendor patches for Wyse Management Suite 3.8 and below. If no patch is available, implement compensating controls such as strict role-based access control validation at the application layer and audit admin user permissions to ensure least privilege principles.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46754 — 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-2022-46754 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