Skip to main content
CVE-2025-29756VulnerabilityPublished Updated

CVE-2025-29756: SunGrow iSolarCloud · Missing Authorization

Affects SunGrow iSolarCloudSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/AU:Y

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
SunGrow iSolarCloudAffected
  • =0
Fixed in–

AI-suggested

Immediate mitigation steps include restricting access to the MQTT broker by implementing strict topic-level authorization controls, ensuring that users can only subscribe to topics associated with their own devices. SunGrow should urgently develop and deploy patches to enforce these restrictions server-side. Organizations should monitor network traffic for unusual MQTT subscription patterns, especially wildcard subscriptions, and implement anomaly detection to identify potential abuse. Additionally, enforcing multi-factor authentication (MFA) on iSolarCloud accounts can reduce the risk of account compromise. Users should be advised to avoid sharing credentials and to regularly update passwords. Where possible, organizations should segment MQTT traffic and isolate critical device data to limit exposure. Until patches are available, organizations might consider limiting access to the iSolarCloud platform or using alternative monitoring solutions. Regular security audits and penetration testing focused on MQTT services are recommended to identify and remediate similar authorization weaknesses.

Description

SunGrow's back end users system iSolarCloud https://isolarcloud.com  uses an MQTT service to transport data from the user's connected devices to the user's web browser.  The MQTT server however did not have sufficient restrictions in place to limit the topics that a user could subscribe to.  While the data that is transmitted through the MQTT server is encrypted and the credentials for the MQTT server are obtained though an API call, the credentials could be used to subscribe to any topic and the encryption key can be used to decrypt all messages received. An attack with an account on iSolarCloud.com could extract MQTT credentials and the decryption key from the browser and then use an external program to subscribe to the topic '#' and thus recieve all messages from all connected devices.

References

Community reviews

Loading reviews…