CVE-2024-50696 json
SunGrow WiNet-S V200.001.00.P025 and earlier versions is missing integrity checks for firmware upgrades.
published 2025-02-26 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-5292
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
SunGrow WiNet-S V200.001.00.P025 and earlier versions is missing integrity checks for firmware upgrades. Sending a specific MQTT message allows an update to an inverter or a WiNet connectivity dongle with a bogus firmware file that is located on attacker-controlled server.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-25-072-12 updated cvss 8.1
Sungrow iSolarCloud Android App, WiNet Firmware
-
Sungrow iSolarCloud Android App <=2.1.6affected: vendor fix, mitigation “For more information refer to Sungrow's security notice.” en.sungrowpower.com
-
Sungrow WiNet Firmwareaffected: mitigation “For more information refer to Sungrow's security notice.” en.sungrowpower.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Classification
- Weakness
-
- CWE-494 Download of Code Without Integrity Check
References
-
en.sungrowpower.com
/security-notice-detail-2/6140
vendor-advisory
Sources
- CVE List CVE-2024-50696
- NVD CVE-2024-50696
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.