dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-2740

HIGH · 8.4 CVSS v3.1 Published 2026-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Zohocorp ManageEngine ADSelfService Plus version before 6525, DataSecurity Plus before 6264 and RecoveryManager Plus before 6313 are vulnerable to Authenticated Remote code execution in the agent machines due to the bug in the 3rd party dependency.

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

This is an authenticated remote code execution vulnerability affecting Zoho ManageEngine ADSelfService Plus, DataSecurity Plus, and RecoveryManager Plus. The flaw exists in a third-party dependency component and allows authenticated attackers to execute arbitrary code on agent machines. All three products ship with vulnerable versions of the same dependency.

MitigationUpgrade to ADSelfService Plus version 6525 or later, DataSecurity Plus version 6264 or later, and RecoveryManager Plus version 6313 or later to address the vulnerable third-party dependency.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L

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 ManageEngine products
    Check your systems for any of these three products: ADSelfService Plus, DataSecurity Plus, or RecoveryManager Plus. Look for their installation directories or installed programs list.
    Affected if Any of these three products are installed on the system
  2. Check installed version of ADSelfService Plus
    Locate the ADSelfService Plus installation and retrieve its version information, typically found in the product UI under About or in a version file within the installation directory.
    Affected if The installed version is lower than 6525
  3. Check installed version of DataSecurity Plus
    Locate the DataSecurity Plus installation and retrieve its version information, typically found in the product UI under About or in a version file within the installation directory.
    Affected if The installed version is lower than 6264
  4. Check installed version of RecoveryManager Plus
    Locate the RecoveryManager Plus installation and retrieve its version information, typically found in the product UI under About or in a version file within the installation directory.
    Affected if The installed version is lower than 6313
  5. Verify presence of agent components
    Check if the product has agent components deployed or configured. Review the product's agent management interface or list of registered agents.
    Affected if Agent machines are registered or connected to any vulnerable product installation

You are affected if any of these three ManageEngine products are installed with versions below their respective thresholds (ADSelfService Plus <6525, DataSecurity Plus <6264, RecoveryManager Plus <6313) and have active agent connections.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ADSelfService Plus version 6525 or later, DataSecurity Plus version 6264 or later, and RecoveryManager Plus version 6313 or later to address the vulnerable third-party dependency.

Recommended fix Moderate confidence

ADSelfService Plus 6525+ | DataSecurity Plus 6264+ | RecoveryManager Plus 6313+

  1. Identify which ManageEngine product is deployed: ADSelfService Plus, DataSecurity Plus, or RecoveryManager Plus
  2. Check the currently installed version of the product
  3. For ADSelfService Plus: Upgrade to version 6525 or later
  4. For DataSecurity Plus: Upgrade to version 6264 or later
  5. For RecoveryManager Plus: Upgrade to version 6313 or later
  6. Download the updated version from the official ManageEngine portal (www.manageengine.com)
  7. Back up the current installation and configuration before upgrading
  8. Apply the upgrade following standard ManageEngine upgrade procedures
Caveat Standard upgrade precautions apply - backup data and configurations before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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