# CVE-2024-36038: Stored XSS

> Attackers can inject malicious scripts via the proxy server option in ManageEngine OpManager, potentially compromising user sessions.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/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:** 24 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-85gq-377h-5g79

## What is CVE-2024-36038?

CVE-2024-36038 is a medium-severity cross-site scripting vulnerability in ManageEngine OpManager, published on 24 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Zoho ManageEngine ITOM products versions from 128234 to 128248 are affected by the stored cross-site scripting vulnerability in the proxy server option.

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

## Which versions are affected by CVE-2024-36038?


## How do I fix CVE-2024-36038?

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

## Is CVE-2024-36038 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36038 and fix it if it is affected.

What it is: CVE-2024-36038 is a medium-severity cross-site scripting vulnerability in ManageEngine OpManager, published on 24 Jun 2024. 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-2024-36038 in the wild and no public exploit code.

Affected product: ManageEngine OpManager. 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-2024-36038/ (Markdown: https://insights.sbomify.com/CVE-2024-36038/index.md)
```

## Sources

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

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