dbcve.org
Manageengine Cloud Security PlusApplication · Zohocorp

CVE-2021-40173

HIGH · 8.8 CVSS v3.1 Published 2021-08-29
Fix available
A fix is available. Upgrade to after 4.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Cloud Security Plus before Build 4117 allows a CSRF attack on the server 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Zoho ManageEngine Cloud Security Plus allows remote attackers to modify server proxy settings by tricking authenticated administrators into unknowingly submitting malicious requests.

MitigationUpgrade to ManageEngine Cloud Security Plus Build 4117 or later to patch the CSRF vulnerability in the proxy settings functionality.

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.0= 4.1

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
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 checks

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

  1. Identify the installed version of Cloud Security Plus
    Access the product admin console and navigate to the About or Settings section, typically found under Help > About or Administration > Product Information. Note the exact version number and build number displayed.
    Affected if The installed version is 4.0 or earlier, or is exactly version 4.1, without having applied the patch from Build 4117.
  2. Confirm the proxy settings functionality is present
    Navigate to the server or network settings area within the admin console. Look for a Proxy Settings, Server Proxy, or Network Proxy configuration section typically found under Administration > Server Settings or Network Settings.
    Affected if The Proxy Settings functionality exists in the product interface and is accessible to authenticated administrators.
  3. Verify current proxy configuration state
    Examine the active proxy settings configuration if any proxy is configured. Document the current proxy host, port, and authentication settings for comparison.
    Affected if Proxy settings are configured or can be configured, indicating the vulnerable endpoint is operational.
  4. Check for unauthorized or unexpected proxy modifications
    Review proxy configuration logs or audit trails if available. Look for any proxy setting changes that were not initiated by an authorized administrator.
    Affected if Any proxy configuration changes exist that were not explicitly made by known administrators, which could indicate exploitation.

The environment is affected if Cloud Security Plus is version 4.0 or earlier, or exactly version 4.1, and the proxy settings functionality is present and 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 a release after 4.0
Interim mitigation

Upgrade to ManageEngine Cloud Security Plus Build 4117 or later to patch the CSRF vulnerability in the proxy settings functionality.

Recommended fix High confidence

Build 4117 or later of ManageEngine Cloud Security Plus

  1. 1. Backup the current ManageEngine Cloud Security Plus configuration and data
  2. 2. Download the fixed build (Build 4117 or later) from the official ManageEngine downloads page at www.manageengine.com
  3. 3. Stop the Cloud Security Plus service before upgrading
  4. 4. Install the new build following the standard upgrade procedure documented by ManageEngine
  5. 5. Restart the Cloud Security Plus service after upgrade completes
  6. 6. Verify that the server proxy settings are accessible and functioning correctly
  7. 7. Confirm the build number reflects the patched version (4117 or higher)

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-40173 — 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-40173 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