LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40175: Zoho ManageEngine Log360 before Build 5219 allows unrestricted file upload with resultant remote code execu...

Zoho ManageEngine Log360 before Build 5219 allows unrestricted file upload with resultant remote code execution.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

ManageEngine Log360 versions before Build 5219 are reported to allow unrestricted file upload that can result in remote code execution. In business terms, a vulnerable Log360 server could potentially be taken over if reachable by an attacker. The source bundle does not provide CVSS, affected CPEs, or detailed exploit conditions.

Executive priority

Prioritize remediation if Log360 is deployed, especially if reachable beyond internal administration networks. Remote code execution in log-management infrastructure can affect sensitive telemetry, credentials, and incident response visibility. Evidence is limited, but the impact class justifies urgent inventory and upgrade action.

Technical view

CVE-2021-40175 describes unrestricted file upload in Zoho ManageEngine Log360 before Build 5219, with resultant remote code execution. The public bundle provides limited technical detail: no CWE, CVSS vector, affected CPE list, exploit prerequisites, or named attack path. The vendor readme reference anchors the build boundary.

Likely exposure

Organizations running Zoho ManageEngine Log360 before Build 5219 are the exposed population. Exposure is higher where the Log360 management interface or upload-capable endpoints are reachable from untrusted networks. The bundle does not identify specific deployment modes, modules, or operating systems.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It also does not provide proof-of-concept status. Treat this as a serious RCE-class issue, but do not claim exploitation without additional sourced evidence.

Researcher notes

The record is sparse: no CVSS, CWE, CPEs, detailed endpoint, authentication requirement, or exploit status is included. Analysis should stay limited to Log360 before Build 5219 and the stated unrestricted upload to RCE impact. Additional vendor material is needed for precise detection engineering.

Mitigation direction

  • Inventory all Zoho ManageEngine Log360 deployments and record build numbers.
  • Upgrade vulnerable Log360 installations to Build 5219 or later, per vendor guidance.
  • Restrict Log360 access to trusted administrative networks and authenticated administrators.
  • Check ManageEngine advisories or support channels for current hardening guidance.
  • Prioritize internet-facing or externally reachable instances first.

Validation and detection

  • Confirm each Log360 instance reports Build 5219 or later.
  • Verify no exposed Log360 administrative interface is reachable from untrusted networks.
  • Review recent upload and administrative activity for unexplained file changes.
  • Check security monitoring for unexpected process execution from Log360 paths.
  • Document any remaining pre-5219 instances with owner, exposure, and remediation date.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-40175 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.