# CVE-2025-36746: SolarEdge Monitoring Platform contains a XSS upon report deletion

> An authenticated user can inject scripts into report names, leading to code execution in a victim's browser during deletion.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L/AU:N/V:D`)
- **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:** 12 Dec 2025
- **Updated:** 6 Jan 2026
- **Also known as:** GHSA-37qv-3hw5-x3ph

## What is CVE-2025-36746?

CVE-2025-36746 is a medium-severity cross-site scripting vulnerability in SolarEdge Monitoring platform (SaaS), published on 12 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SolarEdge monitoring platform contains a Cross‑Site Scripting (XSS) flaw that allows an authenticated user to inject payloads into report names, which may execute in a victim’s browser during a deletion attempt.

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

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

It affects 1 product.


Products: Solaredge Solaredge Monitoring Platform.

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

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

## Is CVE-2025-36746 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-36746 is a medium-severity cross-site scripting vulnerability in SolarEdge Monitoring platform (SaaS), published on 12 Dec 2025. 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-36746 in the wild and no public exploit code.

Affected product: SolarEdge Monitoring platform (SaaS). 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-36746/ (Markdown: https://insights.sbomify.com/CVE-2025-36746/index.md)
```

## Sources

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

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