CVE-2021-40172
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 a CSRF attack on proxy settings.
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 a Cross-Site Request Forgery (CSRF) vulnerability in its proxy settings functionality. An authenticated administrator could be tricked into making unintended changes to proxy configuration via a maliciously crafted link or page.
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.0, <= 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Log360 installation and versionLocate the ManageEngine Log360 installation directory and check the build number. Typically found in the product's About or Help section, or check the installation logs and version file in the product root directory.Affected if The installed version is 5.0, 5.1, or 5.2 (any build before 5219).
-
Confirm the exact build numberAccess the product's About or System Details page within the Log360 admin console, or check the build.info/version.xml file in the installation folder.Affected if The build number is lower than 5219.
-
Verify proxy settings functionality existsNavigate to the Admin/ Settings section in the Log360 web console and locate the Proxy Settings or Network Configuration area.Affected if Proxy settings functionality is present and accessible in the admin interface.
-
Check if proxy is configuredInspect the proxy configuration page to see if any proxy settings are defined or if the feature is actively in use.Affected if Proxy settings are configurable or currently set in the Log360 environment.
A user is affected if they are running ManageEngine Log360 version 5.0, 5.1, or 5.2 with a build number below 5219 and have access to the proxy settings functionality in the admin console.
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 Zoho ManageEngine Log360 to Build 5219 or later to obtain the CSRF protection fix. As an interim measure, educate administrators about not clicking untrusted links while authenticated.
ManageEngine Log360 Build 5219 or later
- Download ManageEngine Log360 Build 5219 or later from the official ManageEngine website
- Ensure you have a backup of current configuration before upgrading
- Follow the standard upgrade procedure for ManageEngine Log360
- Verify the proxy settings can be saved without CSRF vulnerability after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40172 — 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-40172 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