CVE-2025-36746
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 · uneditedSolarEdge 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.
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 · high confidenceSolarEdge monitoring platform contains a stored Cross-Site Scripting (XSS) vulnerability where authenticated users can inject malicious JavaScript payloads into report names. When another user attempts to delete the affected report, the payload executes in their browser, potentially allowing session hijacking or unauthorized actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SolarEdge Monitoring Platform is deployedIdentify whether the SolarEdge Monitoring Platform is installed in your environment. This may be visible in your software inventory, application list, or system documentation.Affected if SolarEdge Monitoring Platform is present - since all versions are affected, you are running a vulnerable version.
-
Verify user authentication is enabledCheck whether user authentication is configured and active for the monitoring platform. The vulnerability requires an authenticated user to inject the malicious payload into report names.Affected if User authentication is enabled - the flaw can be exploited by any authenticated user.
-
Identify report creation functionalityLocate the report management feature in the SolarEdge Monitoring Platform. Look for areas where users can create, name, or modify reports.Affected if Report functionality exists - this is the injection point for the malicious payload.
-
Review existing report names for suspicious contentInspect all report names stored in the system for any unexpected characters, script tags, or encoded payloads that could indicate exploitation attempts.Affected if Any report names contain JavaScript code, script tags, or encoded XSS payloads, the vulnerability has been exploited in your environment.
-
Check browser console logs for XSS errorsIf you have access to the application interface, navigate to the reports section and attempt to delete reports while monitoring the browser developer console for any executed JavaScript or console errors.Affected if JavaScript executes or errors appear when interacting with report deletion, confirming the XSS vulnerability is present.
Your environment is affected if SolarEdge Monitoring Platform is deployed with user authentication enabled, regardless of version, since all versions contain this stored XSS vulnerability in the report name feature.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict input validation and output encoding for all report names, and apply context-aware sanitization before rendering user-supplied content in any browser context. Consider deploying Content Security Policy headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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