# CVE-2025-9226: Stored XSS

> Attackers can inject malicious scripts into Subnet Details, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-rv8x-5qhg-m8hq

## What is CVE-2025-9226?

CVE-2025-9226 is a medium-severity cross-site scripting vulnerability in Zohocorp ManageEngine NetFlow Analyzer, published on 30 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Zohocorp ManageEngine OpManager, NetFlow Analyzer, and OpUtils versions prior to 128582 are affected by a stored cross-site scripting vulnerability in the Subnet Details.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2025-9226 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9226 is a medium-severity cross-site scripting vulnerability in Zohocorp ManageEngine NetFlow Analyzer, published on 30 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-9226 in the wild and no public exploit code.

Affected product: Zohocorp ManageEngine NetFlow Analyzer. 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-9226/ (Markdown: https://insights.sbomify.com/CVE-2025-9226/index.md)
```

## Sources

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

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