CVE-2021-37931
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 · uneditedZoho 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 · high confidenceZoho ManageEngine ADManager Plus versions 7110 and prior contains an unrestricted file upload vulnerability that allows authenticated or unauthenticated attackers to upload malicious files to the server, leading to remote code execution (RCE) with elevated privileges.
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< 7.1= 7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ADManager Plus installation and versionLocate the ADManager Plus installation directory and check the build number in the version file or the application's about/login page. Common locations include the 'build.xml' or 'version.txt' file in the installation root, or the version displayed in the web interface footer.Affected if The installed version is 7110 or lower (build numbers below 7120), indicating the unpatched version is in use.
-
Confirm web management interface is accessibleAttempt to access the ADManager Plus web interface via HTTP/HTTPS on the configured port (typically 8080 or 8443). Check if the login page loads.Affected if The web interface is reachable from the network, providing an attack surface for the file upload vulnerability.
-
Check network exposure of the management portReview firewall rules, reverse proxy configurations, or network segmentation to determine if the ADManager Plus web port is exposed to untrusted networks or the internet.Affected if The management port is exposed to the internet or untrusted internal networks without proper access controls.
-
Verify authentication configurationExamine the application's authentication settings or startup configuration to determine if unauthenticated access is permitted to file upload endpoints.Affected if The application allows unauthenticated file uploads or has weak authentication enforcement.
The environment is affected if ADManager Plus version 7110 or prior is installed and its web interface is network-accessible, enabling remote attackers to upload and execute malicious files.
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 data7.1
Upgrade ManageEngine ADManager Plus to version 7120 or later which contains the vendor patch, or apply available security updates; restrict network access to the management interface as an interim control.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37931 — 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-2021-37931 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