Manageengine Mobile Device Manager PlusApplication · Zohocorp

CVE-2022-41339

HIGH · 7.8 CVSS v3.1 Published 2022-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
In Zoho ManageEngine Mobile Device Manager Plus before 10.1.2207.5, the User Administration module allows privilege escalation.

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

The User Administration module in Zoho ManageEngine Mobile Device Manager Plus (versions before 10.1.2207.5) contains a privilege escalation vulnerability that allows authenticated users to elevate their privileges beyond those assigned to their role, likely gaining administrative access they should not have.

MitigationUpgrade Mobile Device Manager Plus to version 10.1.2207.5 or later to remediate this vulnerability. Until the patch is applied, restrict User Administration module access to only trusted administrative personnel and monitor for unauthorized privilege changes.

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
Manageengine Mobile Device Manager PlusApplication
Affected:= 10.1.2207.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 installed version of ManageEngine MDMP
    Access the MDMP admin console, typically at https://<server>:8383 or check the installation directory for version info in about or settings pages
    Affected if Installed version equals 10.1.2207.4 or is earlier than 10.1.2207.5
  2. Confirm User Administration module is accessible
    Log into the MDMP console and navigate to the User Administration or Users & Devices section. Check if the module is present and loadable in the interface
    Affected if User Administration module is present and accessible to the authenticated user account you are testing with
  3. Verify user role permissions
    Review the role assigned to your test account in the User Administration module. Check what privileges the role grants - particularly whether it permits viewing or modifying user accounts
    Affected if Your authenticated account has a non-administrative or limited role but can access User Administration functions
  4. Check for unauthorized privilege changes
    Review audit logs or user activity logs within the MDMP console for any recent changes to user roles, permissions, or account privilege levels that were not initiated by primary administrators
    Affected if There are user privilege modifications that cannot be attributed to legitimate administrator actions

You are affected if MDMP version is 10.1.2207.4 and the User Administration module is accessible to authenticated users with limited privileges, or if unauthorized privilege escalation has occurred in the logs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mobile Device Manager Plus to version 10.1.2207.5 or later to remediate this vulnerability. Until the patch is applied, restrict User Administration module access to only trusted administrative personnel and monitor for unauthorized privilege changes.

Recommended fix High confidence

10.1.2207.5

  1. Backup the current ManageEngine Mobile Device Manager Plus installation and database
  2. Download version 10.1.2207.5 from the official ManageEngine downloads page (www.manageengine.com)
  3. Stop the Mobile Device Manager Plus service
  4. Install the upgrade to version 10.1.2207.5 following standard installation procedures
  5. Start the Mobile Device Manager Plus service
  6. Verify the User Administration module is functioning correctly and the privilege escalation vulnerability is resolved

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

Fix this in Manageengine Mobile Device Manager Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41339 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41339 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