Manageengine Admanager PlusApplication · Zohocorp

CVE-2021-37918

CRITICAL · 9.8 CVSS v3.1 Published 2021-10-07
Fix available
A fix is available. Upgrade to 7.1 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges 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
Zoho ManageEngine ADManager Plus version 7110 and prior allows unrestricted file upload which leads to remote code execution.

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

Zoho ManageEngine ADManager Plus versions 7110 and prior contains an unrestricted file upload vulnerability in its web interface. An attacker can upload malicious files (such as web shells) to the server without proper validation, leading to remote code execution.

MitigationUpgrade ManageEngine ADManager Plus to a version newer than 7110. If immediate patching is not possible, restrict network access to the application's management interface and monitor for suspicious file uploads.

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 Admanager PlusApplication
Affected:< 7.1= 7.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm ADManager Plus installation and locate version file
    Navigate to the ADManager Plus installation directory (commonly C:\ManageEngine\ADManager Plus or /opt/ManageEngine/ADManagerPlus) and locate the version.txt or build.txt file. Alternatively, access the application's About page via the web interface at /jsp/index.jsp or /home.jsp and look for the build number.
    Affected if The installed build number is 7110 or lower (for example, 7100, 7080, etc.)
  2. Check the build number in product.conf
    In the installation directory, open the conf/product.conf file and look for the 'buildNumber' or 'version' entry. ManageEngine uses build numbers rather than semantic versioning.
    Affected if The buildNumber value is 7110 or less
  3. Verify the running service version via Windows Registry or process
    On Windows, check the installed version via Registry at HKEY_LOCAL_MACHINE\SOFTWARE\ManageEngine\ADManager Plus or by examining the running ADManager Plus service process properties. On Linux, check the running process or service for version indicators.
    Affected if The registered or running version shows 7110 or prior
  4. Identify web interface exposure
    Determine if the ADManager Plus web interface (default ports 8080 or 8443) is accessible from untrusted networks. Check firewall rules, reverse proxy configurations, and network segmentation around the server.
    Affected if Port 8080/8443 or the configured web port is open to the internet or untrusted internal networks without proper access controls
  5. Audit uploaded files in the web root
    Inspect the directory where uploaded files are stored (typically the 'work' or 'temp' subdirectories within the ADManager Plus installation) for unexpected .jsp, .asp, .php, or executable files with suspicious names or recent creation timestamps.
    Affected if Unexpected script files (especially .jsp shells) or executables are found in upload directories with dates coinciding with potential exploitation

The environment is affected if ManageEngine ADManager Plus build number is 7110 or lower AND the web interface is network-accessible to potential attackers.

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.

From vendor data
Upgrade available Upgrade to 7.1 or later
Fixed in 7.1
Interim mitigation

Upgrade ManageEngine ADManager Plus to a version newer than 7110. If immediate patching is not possible, restrict network access to the application's management interface and monitor for suspicious file uploads.

Fix this in Manageengine Admanager Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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