dbcve.org
Manageengine OpmanagerApplication · Zohocorp

CVE-2020-10541

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-13
Fix available
A fix is available. Upgrade to 12.4.179 or later.
See remediation →
100/100
Remediation priority · Urgent
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 12.4.179 allows remote code execution via a specially crafted Mail Server Settings v1 API request. This was fixed in 12.5.108.

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 OpManager before version 12.4.179 contains a remote code execution vulnerability in the Mail Server Settings v1 API. The vulnerability is exploitable through specially crafted API requests, allowing an attacker to execute arbitrary code on the target system without authentication.

MitigationUpgrade ManageEngine OpManager to version 12.5.108 or later. If immediate patching is not possible, restrict network access to the OpManager management interface to trusted sources only.

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.4.179

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. Identify if ManageEngine OpManager is installed
    Look for the OpManager service/process on the system, or check for its installation directory (commonly at C:\Program Files\ManageEngine\OpManager or /opt/ManageEngine/OpManager on Linux)
    Affected if OpManager is found running on the system
  2. Determine the installed OpManager version
    Access the OpManager web interface and navigate to the About page, or check the version.txt or version.info file in the OpManager installation directory
    Affected if The discovered version is less than 12.4.179
  3. Verify the Mail Server Settings API endpoint is accessible
    Send an HTTP request to the /api/json/v1/settings/mailserver or similar endpoint on the OpManager host (default port 8080) without authentication
    Affected if The API responds and accepts requests without authentication
  4. Check if OpManager is exposed to untrusted networks
    Review firewall rules or network configuration to determine if the OpManager web interface (port 8080 or configured port) is accessible from untrusted networks
    Affected if Port 8080 or the OpManager port is open to the internet or untrusted networks

If OpManager is running with a version lower than 12.4.179 and its Mail Server Settings API is accessible from the network, the system is affected by this vulnerability.

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.4.179 or later
Fixed in 12.4.179
Interim mitigation

Upgrade ManageEngine OpManager to version 12.5.108 or later. If immediate patching is not possible, restrict network access to the OpManager management interface to trusted sources only.

Recommended fix High confidence

ManageEngine OpManager 12.5.108 or later

  1. 1. Back up the current OpManager installation and database before upgrading.
  2. 2. Download ManageEngine OpManager version 12.5.108 or later from the official ManageEngine download page.
  3. 3. Stop the OpManager service before beginning the upgrade process.
  4. 4. Run the installer/upgrade utility to update to version 12.5.108 or newer.
  5. 5. Start the OpManager service after the upgrade completes.
  6. 6. Verify the Mail Server Settings v1 API functionality is working correctly after the upgrade.
  7. 7. Confirm the OpManager web interface is accessible and all services are running normally.
Caveat Review release notes for any changes to API endpoints or functionality between your current version and 12.5.108

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

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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