dbcve.org
Manageengine Cloud Security PlusApplication · Zohocorp

CVE-2021-44651

HIGH · 8.8 CVSS v3.1 Published 2022-01-12
Fix available
A fix is available. Upgrade to 4.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Zoho ManageEngine CloudSecurityPlus before Build 4117 allows remote code execution through the updatePersonalizeSettings component due to an improper security patch for CVE-2021-40175.

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 confidence

Zoho ManageEngine CloudSecurityPlus before Build 4117 contains a remote code execution vulnerability in the updatePersonalizeSettings component. This issue stems from an incomplete or improper security patch for the earlier CVE-2021-40175, allowing authenticated attackers to execute arbitrary code on the affected system.

MitigationUpgrade ManageEngine CloudSecurityPlus to Build 4117 or later to obtain the complete security patch. If immediate patching is not possible, restrict network access to the administrative interface and review access logs for indicators of compromise.

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
Manageengine Cloud Security PlusApplication
Affected:< 4.1= 4.1<= 4.1.1.7
Log360Application
Affected:<= 5.2.2

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product
    Check whether Zoho ManageEngine CloudSecurityPlus or Log360 is installed. Look for installation directories or running services named 'CloudSecurityPlus' or 'Log360'.
    Affected if Either CloudSecurityPlus with version/build below 4117, or Log360 version 5.2.2 or below is installed.
  2. Check CloudSecurityPlus build version
    Navigate to the CloudSecurityPlus web interface, then go to Settings > About or check the build number in the installation directory (typically in a version or buildinfo file). Compare the build number to 4117.
    Affected if Build number is less than 4117 (vulnerable). Versions < 4.1, = 4.1, or <= 4.1.1.7 are affected.
  3. Check Log360 version
    Navigate to the Log360 web interface, go to Settings > About or check the version in the installation directory. Compare the version to 5.2.2.
    Affected if Version is 5.2.2 or lower.
  4. Verify updatePersonalizeSettings component accessibility
    Attempt to access the /updatePersonalizeSettings endpoint via HTTP GET or POST request to the application's administrative interface using valid administrator credentials.
    Affected if The endpoint responds and accepts requests (component is exposed and functional).
  5. Confirm authentication is required
    Review the application's authentication configuration and verify whether the updatePersonalizeSettings component enforces authentication. Attempt an unauthenticated request to the endpoint.
    Affected if The component processes requests from authenticated users (attack requires valid admin credentials).

The environment is affected if CloudSecurityPlus build is below 4117 (or version <= 4.1.1.7), or Log360 version is <= 5.2.2, and the updatePersonalizeSettings component is accessible to authenticated administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.1 or later
Fixed in 4.1
Interim mitigation

Upgrade ManageEngine CloudSecurityPlus to Build 4117 or later to obtain the complete security patch. If immediate patching is not possible, restrict network access to the administrative interface and review access logs for indicators of compromise.

Recommended fix High confidence

ManageEngine Cloud Security Plus Build 4117 or later (note: Log360 <=5.2.2 also affected but specific fixed version not specified in available sources)

  1. 1. Back up the current ManageEngine Cloud Security Plus installation and configuration
  2. 2. Download the latest version of ManageEngine Cloud Security Plus (Build 4117 or later) from the official ManageEngine download portal
  3. 3. Stop the Cloud Security Plus service before applying the update
  4. 4. Install the updated build following the vendor's standard upgrade procedure
  5. 5. Verify the updatePersonalizeSettings component is no longer vulnerable to unrestricted file upload
  6. 6. Restart the Cloud Security Plus service
  7. 7. Confirm the application is functioning normally post-upgrade
Caveat Standard upgrade precautions apply - back up data before upgrading; test in staging environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manageengine Cloud Security Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-44651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-44651 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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