dbcve.org
Manageengine Endpoint CentralApplication · Zohocorp

CVE-2025-5494

HIGH · 7.8 CVSS v3.1 Published 2025-09-25
Fix available
A fix is available. Upgrade to 11.4.2500.26 / 11.4.2508.14 or later.
See remediation →
80/100
Remediation priority · High
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 Endpoint Central was impacted by an improper privilege management issue in the agent setup. This issue affects Endpoint Central: through 11.4.2500.25, through 11.4.2508.13.

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 · moderate confidence

ManageEngine Endpoint Central agent setup contains an improper privilege management issue that allows low-privilege users to potentially escalate privileges during or after agent installation. This local privilege escalation vulnerability stems from insufficient validation or enforcement of privilege boundaries during the agent setup process.

MitigationUpdate Endpoint Central to a version beyond 11.4.2508.13 (or the latest stable release) which contains the vendor patch for this privilege management vulnerability.

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 Endpoint CentralApplication
Affected:< 11.4.2500.26>= 11.4.2508.01, < 11.4.2508.14

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

CVSS:3.1/AV:L/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. Locate Endpoint Central installation directory
    Identify where ManageEngine Endpoint Central is installed. Common paths include C:\Program Files\ManageEngine\EndpointCentral or C:\ManageEngine\EndpointCentral on Windows, or /opt/ManageEngine/EndpointCentral on Linux. Check for the presence of the agent executable or installation folder.
    Affected if Endpoint Central agent is installed on the system
  2. Identify installed Endpoint Central version
    Locate the version information file or executable (often named EndpointCentral.exe, dcagent.exe, or a version.txt/version.ini file within the installation directory). Open it to read the exact version number installed.
    Affected if The installed version matches < 11.4.2500.26 OR is >= 11.4.2508.01 but < 11.4.2508.14
  3. Confirm agent setup component presence
    Check for the presence of agent setup or installation components within the Endpoint Central directory structure. Look for agent-related executables, configuration files, or setup logs that indicate the agent installation process is or was present.
    Affected if The agent setup components exist on the system and the version from step 2 falls within the vulnerable ranges
  4. Check for low-privilege user access to agent directories
    Review file system permissions on the Endpoint Central agent installation directories. Verify if standard non-admin users have write or modify access to agent directories, configuration files, or executables used during or after the installation process.
    Affected if Non-privileged users have elevated file system permissions to agent components, indicating the privilege boundary issue exists

A system is affected if Endpoint Central agent is installed with a version less than 11.4.2500.26 or between 11.4.2508.01 and 11.4.2508.13 inclusive.

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 11.4.2500.26 / 11.4.2508.14 or later
Fixed in 11.4.2500.2611.4.2508.14
Interim mitigation

Update Endpoint Central to a version beyond 11.4.2508.13 (or the latest stable release) which contains the vendor patch for this privilege management vulnerability.

Recommended fix High confidence

11.4.2500.26 (for older branch) or 11.4.2508.14 (for newer branch)

  1. 1. Identify the currently installed ManageEngine Endpoint Central version from the admin console or server.
  2. 2. If the installed version is < 11.4.2500.26, plan upgrade to version 11.4.2500.26 or later.
  3. 3. If the installed version is >= 11.4.2508.01 and < 11.4.2508.14, plan upgrade to version 11.4.2508.14 or later.
  4. 4. Before upgrading, backup the Endpoint Central database and configuration files.
  5. 5. Download the appropriate updated version from the official ManageEngine download portal.
  6. 6. Apply the upgrade during a maintenance window following ManageEngine's standard upgrade procedure.
  7. 7. After upgrade, verify the agent setup functionality and confirm the version change was successful.
Caveat Standard upgrade precautions apply - test in non-production first, backup data, and ensure compatible dependencies

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

Fix this in Manageengine Endpoint Central Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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