SolarEdge Monitoring Platform - Framework /Solaredge-Web/ — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/solaredge-monitoring-platform---framework-/solaredge-web/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 21 May 2026 13:32:19 +0000SolarEdge CSRF and Out-of-Band Injection Vulnerabilityhttps://feed.craftedsignal.io/briefs/2026-05-solaredge-csrf-oob-injection/Thu, 21 May 2026 13:32:19 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-solaredge-csrf-oob-injection/A CSRF-OOB-Injection vulnerability exists in SolarEdge Monitoring Platform's `/solaredge-web/p/initClient` endpoint due to improper validation of session parameters, allowing attackers to manipulate headers to initiate requests to attacker-controlled domains, potentially leading to session compromise and unauthorized system control.A cross-site request forgery (CSRF) and out-of-band (OOB) injection vulnerability has been identified in the SolarEdge Monitoring Platform, specifically affecting the /solaredge-web/p/initClient endpoint. The vulnerability, discovered by nu11secur1ty, stems from a business logic flaw that allows the generation and overwriting of session parameters without proper origin validation. An attacker can leverage this vulnerability to force a legitimate operator’s browser to execute unauthorized commands. Additionally, by manipulating the X-Forwarded-For and Referer headers, an attacker can force the SolarEdge internal infrastructure to initiate requests to external, attacker-controlled domains, demonstrating a lack of framework-level filtration. This could lead to session compromise and potential unauthorized control over photovoltaic systems.

Attack Chain

  1. Attacker crafts a malicious HTML page containing a POST request to /solaredge-web/p/initClient with the cmd=createCookie parameter.
  2. The crafted POST request sets arbitrary session parameters due to the lack of CSRF protection.
  3. The attacker manipulates the X-Forwarded-For header to point to an attacker-controlled domain (e.g., cn3iam50ywo00n2a5vvi3o59r0xrln9c.oastify.com).
  4. The attacker may also manipulate the Referer header to further control the request’s origin.
  5. A victim user visits the attacker-controlled webpage, triggering the CSRF attack.
  6. The victim’s browser sends the crafted POST request to the SolarEdge Monitoring Platform.
  7. The SolarEdge infrastructure initiates an out-of-band request to the attacker-controlled domain specified in the X-Forwarded-For header.
  8. The attacker gains unauthorized access to the SolarEdge platform through session hijacking or gains information about the internal infrastructure.

Impact

Successful exploitation of this vulnerability could allow an attacker to hijack legitimate user sessions on the SolarEdge Monitoring Platform. This can lead to unauthorized monitoring, modification, or control of physical photovoltaic systems managed through the platform. An attacker could potentially disrupt energy production, tamper with system settings, or gain access to sensitive data. The lack of specific victim count or sector information limits a precise impact assessment.

Recommendation

  • Implement CSRF protection measures on the /solaredge-web/p/initClient endpoint to prevent unauthorized session parameter manipulation, mitigating the primary CSRF vulnerability described in the Overview.
  • Sanitize and validate the X-Forwarded-For and Referer headers to prevent out-of-band injection attacks, blocking requests to attacker-controlled domains such as cn3iam50ywo00n2a5vvi3o59r0xrln9c.oastify.com (IOC).
  • Deploy the Sigma rule “Detect SolarEdge Out-of-Band Injection via X-Forwarded-For” to identify attempts to exploit this vulnerability in web server logs.
]]>mediumthreatsolaredgecsrfoob-injectionwebapps