dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-9223

HIGH · 8.8 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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 Applications Manager versions 178100 and below are vulnerable to authenticated command injection vulnerability due to the improper configuration in the execute program action feature.

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

Authenticated command injection vulnerability in Zoho ManageEngine Applications Manager's execute program action feature (versions 178100 and below) allows authenticated users to execute arbitrary commands due to improper configuration.

MitigationUpgrade to a version above 178100, or restrict and properly configure access to the execute program action feature.

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

CVSS:3.1/AV:N/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. Confirm Zoho ManageEngine Applications Manager is installed
    Locate the Applications Manager installation directory or check running services for 'ApplicationsManager' or 'AppManager' processes
    Affected if The product is present in the environment
  2. Identify the installed version number
    Check the build number in the product's 'build.txt' or 'version.info' file, typically found in the installation root directory, or access the About page in the admin console
    Affected if The version/build number is 178100 or lower
  3. Determine if the execute program action feature is enabled
    Log into the Applications Manager admin console and navigate to the Actions or Tools configuration section to verify if 'Execute Program' action is available or enabled for monitoring tasks
    Affected if The execute program action feature is enabled and accessible to users
  4. Check user access to the execute program action feature
    Review user roles and permissions in the Admin section to see which authenticated users or user groups have privileges to use the Execute Program action
    Affected if Authenticated users with limited privileges can access the execute program action feature

The environment is affected if Zoho ManageEngine Applications Manager version 178100 or below is running with the execute program action feature enabled and accessible to authenticated users.

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 a version above 178100, or restrict and properly configure access to the execute program action feature.

Recommended fix Moderate confidence

Latest available build of ManageEngine Applications Manager (build version higher than 178100)

  1. 1. Identify your current ManageEngine Applications Manager build version in the product UI or via the 'buildnumber.txt' file in the installation directory.
  2. 2. Confirm your current version is 178100 or below, which is affected by this vulnerability.
  3. 3. Contact ManageEngine official support or visit www.manageengine.com to obtain the latest patched build for Applications Manager.
  4. 4. Before upgrading, backup the Applications Manager database and configuration files according to standard backup procedures.
  5. 5. Stop the Applications Manager services before performing the upgrade.
  6. 6. Apply the latest patch or upgrade to a build version higher than 178100 that contains the security fix.
  7. 7. After upgrade, restart the Applications Manager services.
  8. 8. Verify the 'execute program action' feature works correctly with the patched version.
Caveat Review release notes for any configuration or feature changes between your current version and the target upgrade version

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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