CVE-2021-40178
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 5224 allows stored XSS via the LOGO_PATH key value in the logon 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 · moderate confidenceZoho ManageEngine Log360 before Build 5224 contains a stored cross-site scripting (XSS) vulnerability in the logon settings functionality. Attackers can inject malicious JavaScript code through the LOGO_PATH parameter value, which is stored and executed when users view the affected logon settings 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.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.
-
Identify Log360 installation and versionLocate the Log360 installation directory and check the build version. Common paths include C:\Program Files\ManageEngine\Log360 or /opt/ManageEngine/Log360. Look for a build.info, version.txt, or similar file that displays the build number (e.g., Build 5224). Alternatively, access the Log360 admin console and navigate to About or Settings to view the version information.Affected if The installed version is Log360 5.1 or earlier, or Log360 5.2, and the build number is below 5224.
-
Confirm build number is below thresholdIf the version displays as 5.2, verify the specific build number. The fix was implemented in Build 5224. Check the admin console's build information or the build.info file in the installation directory to confirm the exact build number.Affected if The build number is less than 5224 for any 5.x version.
-
Access logon settings configurationLog in to the Log360 admin console with administrative privileges. Navigate to Settings or Administration and locate the Logon Settings or Custom Login configuration area. This is where the LOGO_PATH parameter is managed.Affected if The logon settings page is accessible and displays configuration options for custom login branding.
-
Inspect LOGO_PATH parameter valueIn the logon settings configuration, locate the LOGO_PATH field or any field controlling the login logo path. Examine the current value to see if it contains unexpected characters such as <script>, javascript:, onerror=, onload=, or other HTML/JavaScript code fragments.Affected if The LOGO_PATH parameter contains any embedded JavaScript code, HTML tags, or suspicious URL values that could execute malicious scripts when the login page is rendered.
-
Verify stored XSS execution contextView the actual login page of Log360 (not just the settings page). Inspect the page source or use browser developer tools to examine how the LOGO_PATH value is rendered. Check if user-supplied values are properly escaped or rendered as raw HTML/JavaScript.Affected if The logo or branding element on the login page executes JavaScript code or renders HTML markup from the stored LOGO_PATH value without proper sanitization.
A user is affected if Log360 version is 5.1 or earlier, or 5.2 with build number below 5224, AND the logon settings contain unsanitized script content in the LOGO_PATH parameter that executes when the login page loads.
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 ManageEngine Log360 to Build 5224 or later to remediate the stored XSS vulnerability in the LOGO_PATH parameter of logon settings.
ManageEngine Log360 Build 5224 or later
- 1. Back up the current ManageEngine Log360 configuration and database
- 2. Download Log360 Build 5224 or later from the official ManageEngine download portal (www.manageengine.com)
- 3. Stop the Log360 service before upgrading
- 4. Install the upgraded version (Build 5224 or later) following standard upgrade procedures
- 5. Verify the upgrade was successful by logging into the admin console
- 6. Confirm the LOGO_PATH parameter in logon settings is now properly sanitized to mitigate the XSS vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40178 — 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-40178 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