CVE-2021-40176
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 5225 allows stored XSS.
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 confidenceZoho ManageEngine Log360 before Build 5225 contains a stored Cross-Site Scripting (XSS) vulnerability. This allows an attacker to inject malicious JavaScript code that is permanently stored on the server and executes when other users access the affected functionality, potentially leading to session hijacking or credential theft.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Confirm Log360 installation and locate web interfaceIdentify the Log360 instance by accessing its web management console (typically on port 8080 or 8443). Note the URL/IP of the server running Log360.Affected if Log360 is accessible on the network without prior verification of version.
-
Determine installed version and build numberLocate the version information in the Log360 admin console, usually found in the About section, Help menu, or System Information page. Note both the version number (e.g., 5.1, 5.2) and the build number.Affected if The version is 5.1 or lower, or the version is exactly 5.2 with a build number below 5225.
-
Compare against affected version rangesReview the documented version and build: versions <= 5.1 or version = 5.2 with build < 5225 are affected. Any version 5.2 with build >= 5225, or version > 5.2, is NOT affected.Affected if The installed version falls within <= 5.1 or = 5.2 with build < 5225.
-
Identify user input fields that store and display dataIn the Log360 interface, locate functionality that accepts user-supplied input and stores it for later display (such as report names, custom filters, alert descriptions, or user profile fields). These are potential injection points for stored XSS.Affected if The affected functionality (any field that stores and renders user input) is available and users can input custom data.
-
Verify stored XSS execution potentialTest whether data entered into input fields is rendered with proper encoding when viewed by other users. If the application displays stored data without sanitization, the stored XSS vulnerability is present and exploitable.Affected if User-supplied data is rendered unescaped in the browser, allowing JavaScript execution.
A Log360 installation is affected if it runs version 5.1 or lower, or version 5.2 with a build number below 5225, and has user input functionality that stores and displays data without proper encoding.
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 Log360 to Build 5225 or later to patch the stored XSS vulnerability. Additionally, implement output encoding and input validation for all user-supplied data to prevent similar issues.
Build 5225 or later
- Identify current installed build version of ManageEngine Log360
- Access the ManageEngine Log360 admin console
- Navigate to the Updates or About section to confirm the current build number
- If build is 5224 or earlier (including all 5.1.x and 5.2.x versions), download the patched build 5225 or later from the official ManageEngine download portal
- Backup the current Log360 configuration and database
- Execute the upgrade installer for the new build
- Verify the upgrade completed successfully
- Confirm the new build number displays 5225 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40176 — 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-40176 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