# CVE-2025-9223: Command Injection

> Authenticated attackers can execute arbitrary commands via the execute program action feature in ManageEngine Applications Manager.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-pg3q-qhg7-vjw9

## What is CVE-2025-9223?

CVE-2025-9223 is a high-severity command injection vulnerability in Zohocorp ManageEngine Applications Manager, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-9223?


## How do I fix CVE-2025-9223?

No fix has been published for CVE-2025-9223 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9223 being exploited?

There is no known exploitation of CVE-2025-9223 in the wild and no public exploit code.

Public exploit code:

- POC CVE-2025-9223 (github_poc): https://github.com/networkkiller/CVE-2025-9223

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9223 and fix it if it is affected.

What it is: CVE-2025-9223 is a high-severity command injection vulnerability in Zohocorp ManageEngine Applications Manager, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9223 in the wild and no public exploit code.

Affected product: Zohocorp ManageEngine Applications Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9223/ (Markdown: https://insights.sbomify.com/CVE-2025-9223/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9223
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9223
- OSV: https://osv.dev/vulnerability/CVE-2025-9223

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9223/
Summaries are generated and may contain mistakes; the official description above is the record.