dbcve.org
Manageengine OpmanagerApplication · Zohocorp

CVE-2021-40493

CRITICAL · 9.8 CVSS v3.1 Published 2021-10-13
Fix available
A fix is available. Upgrade to 12.5 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges 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 OpManager before 125437 is vulnerable to SQL Injection in the support diagnostics module. This occurs via the pollingObject parameter of the getDataCollectionFailureReason API.

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

SQL injection vulnerability in Zoho ManageEngine OpManager's support diagnostics module allows unauthenticated remote attackers to inject malicious SQL queries via the pollingObject parameter in the getDataCollectionFailureReason API, potentially enabling data exfiltration or database compromise.

MitigationUpgrade ManageEngine OpManager to version 125437 or later to apply the vendor patch. If immediate upgrade is not feasible, restrict network access to the support diagnostics module as a temporary compensating control.

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 OpmanagerApplication
Affected:< 12.5= 12.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm OpManager is installed
    Locate the OpManager installation directory (commonly C:\Program Files\ManageEngine\OpManager or /opt/ManageEngine/OpManager) and check for the presence of OpManager files and scripts (startOpManager.sh or OpManager.exe).
    Affected if OpManager is present on the system.
  2. Identify installed OpManager version
    Check the version file in the installation directory, typically found in the build folder or displayed when running 'OpManager -version' from the bin directory. On Windows, inspect the OpManager.exe properties. On Linux/Unix, check the version.txt or build number file.
    Affected if The installed version is 12.5 or any version below 12.5 (for example, 12.4, 12.3, earlier releases).
  3. Verify support diagnostics module accessibility
    Attempt to access the support diagnostics module endpoint. The vulnerable API is typically at /api/json/s.Diagnostics.getDataCollectionFailureReason or similar paths under the /supportDiagnostics or /api/sDiagnostics/ endpoints. Use curl or a browser to check if the endpoint responds.
    Affected if The support diagnostics API endpoint is reachable without authentication and returns a response.
  4. Check if getDataCollectionFailureReason API responds
    Send a request to the vulnerable API endpoint with a test parameter: curl -X POST 'http://<opmanager-host>:<port>/api/json/s.Diagnostics/getDataCollectionFailureReason' -d 'pollingObject=test' (adjust path based on your installation). Look for SQL error messages or unexpected behavior in the response.
    Affected if The API accepts the pollingObject parameter and returns data without requiring authentication.

You are affected if OpManager version 12.5 or earlier is installed and the unauthenticated support diagnostics API endpoint (getDataCollectionFailureReason) is accessible on your network.

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 12.5 or later
Fixed in 12.5
Interim mitigation

Upgrade ManageEngine OpManager to version 125437 or later to apply the vendor patch. If immediate upgrade is not feasible, restrict network access to the support diagnostics module as a temporary compensating control.

Recommended fix Moderate confidence

Upgrade to build 125437 or later stable release of OpManager (post-version 12.5)

  1. 1. Identify the current installed build version of ManageEngine OpManager
  2. 2. Navigate to the Zoho ManageEngine support portal or official download page to obtain the fixed version
  3. 3. If current version is 12.5 or below (specifically builds before 125437), plan for upgrade to build 125437 or later
  4. 4. Before upgrading, perform a complete backup of the OpManager database and configuration
  5. 5. Schedule the upgrade during a maintenance window to minimize business impact
  6. 6. Download and apply the upgraded version (build 125437 or later stable release)
  7. 7. After upgrade, verify the getDataCollectionFailureReason API is accessible and functioning correctly
  8. 8. Confirm the SQL injection vulnerability is remediated by testing the pollingObject parameter with benign input
Caveat Review release notes for build 125437+ for any configuration or feature changes that may require adjustment; standard practice to test in non-production first

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

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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