CVE-2021-37922
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 is vulnerable to path traversal which allows copying of files from one directory to another.
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 confidenceA path traversal vulnerability in Zoho ManageEngine ADManager Plus versions 7110 and prior allows attackers to copy files between directories by manipulating file paths with traversal sequences (such as '../'). This could enable unauthorized file placement in sensitive system locations.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 the installed ADManager Plus versionAccess the ADManager Plus web interface, go to Settings > Product Settings > About page, or check the build number in the installation directory. Alternatively, check the 'build.txt' or 'version.txt' file in the product installation folder.Affected if The installed version is 7110 or any version prior to 7.1 (e.g., 7100, 7000, etc.)
-
Verify the file copy operation is accessibleConfirm that the ADManager Plus application is running and the file management or reporting features that involve file operations are accessible to users. Path traversal requires the affected file copy functionality to be reachable.Affected if The file copy or file transfer feature is enabled and accessible without additional authentication beyond standard application login.
-
Review access controls on file operation endpointsCheck the application's configuration or security settings to determine if strict access controls are applied to file operation APIs or endpoints. Look for settings controlling who can perform file copy or export operations.Affected if Users with standard application access (non-admin) can invoke file copy operations or if no role-based restrictions exist on file manipulation features.
-
Inspect application logs for traversal attemptsReview ADManager Plus server logs in the 'logs' or 'analytics' directory for requests containing '../' sequences in file path parameters. Look for patterns involving directory traversal in recent activity.Affected if Recent logs show directory traversal patterns in file operation requests, indicating potential exploitation attempts.
A user is affected if their installed ADManager Plus version is 7.1 (build 7110) or earlier AND the file copy feature is accessible to users without additional restrictions on path parameters.
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 · scoped7.1
Upgrade ADManager Plus to a version newer than 7110, or implement strict input validation on file path parameters to reject directory traversal sequences like '..'
ADManager Plus version 7.2 or later (or the latest stable release)
- 1. Back up the current ADManager Plus installation and configuration
- 2. Download the latest version of ManageEngine ADManager Plus from the official ManageEngine website
- 3. Stop the ADManager Plus service before upgrading
- 4. Install the new version following standard upgrade procedures
- 5. Verify the path traversal vulnerability is resolved by testing file operations
- 6. Restart the ADManager Plus service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37922 — 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-37922 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