CVE-2021-40175
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 Log360 before Build 5219 allows unrestricted file upload with resultant 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 Log360 before Build 5219 contains an unrestricted file upload vulnerability that allows unauthenticated attackers to upload arbitrary files to the server, which can result in remote code execution (RCE) on the affected system.
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<= 5.1= 5.2CVSS 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.
-
Locate the installed Log360 versionAccess the Log360 admin console or check the product's About/Version information page to find the currently installed build number and version stringAffected if The displayed version is 5.1 or lower, or exactly 5.2, indicating it is within the vulnerable version range (<=5.1 or =5.2)
-
Identify the specific build numberCheck the build or patch level information in the product's system information or version details panel, often accessible via Help > About in the admin interfaceAffected if The build number is below 5219 (for example, build 5210, 5200, or any build earlier than 5219)
A system is affected if it runs Log360 version 5.1 or lower, or exactly version 5.2, with a build number earlier than 5219, as these versions lack the restriction on file uploads that was fixed in build 5219.
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 · scopedUpgrade to ManageEngine Log360 Build 5219 or later to remediate the vulnerability; implement web application firewall rules and network segmentation as interim compensating controls.
ManageEngine Log360 Build 5219 or later
- 1. Back up your current ManageEngine Log360 installation and database before proceeding with the upgrade.
- 2. Download the latest ManageEngine Log360 build from the official ManageEngine download page (www.manageengine.com) or your licensed download link.
- 3. Ensure you obtain Build 5219 or later as the fixed release.
- 4. Stop the ManageEngine Log360 service before performing the upgrade.
- 5. Run the installer for Build 5219 or later on your Log360 server.
- 6. Follow the on-screen installation prompts, selecting the upgrade option to preserve existing configurations.
- 7. After installation completes, start the Log360 service.
- 8. Verify the build number in the About section matches the fixed release (5219 or later).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40175 — 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-40175 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