dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-29756

HIGH · 8.3 CVSS v4.0 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
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.

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 confidence

SunGrow's iSolarCloud MQTT service lacked topic-based access controls, allowing authenticated users to extract MQTT credentials and decryption keys from the browser and subscribe to the '#' wildcard topic, thereby intercepting all device communications across the entire platform.

MitigationImplement MQTT topic ACLs to restrict users to only their authorized device topics, and review credential/key handling to prevent extraction of valid credentials from the client-side.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
Y
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if iSolarCloud MQTT service is running
    Check for processes or services named iSolarCloud, mqtt, or running on typical MQTT ports (1883, 8883). Use commands like 'ps aux | grep -i solar' or 'netstat -anp | grep mqtt' to locate the service.
    Affected if The iSolarCloud MQTT service is present and running in the environment.
  2. Inspect MQTT broker ACL configuration
    Examine the MQTT broker configuration files (e.g., mosquitto.conf, ACL files) for presence and enforcement of topic access control lists. Look for 'acl_file' or 'pattern' directives that restrict user-level topic subscriptions.
    Affected if No ACL configuration exists or the broker allows unrestricted wildcard subscriptions.
  3. Test if '#' wildcard topic is accessible
    Using an authenticated MQTT client (such as mosquitto_sub or an MQTT explorer tool), attempt to subscribe to the '#' topic with standard user credentials. If the subscription succeeds without error, wildcard access is permitted.
    Affected if The subscription to '#' topic succeeds and returns messages from other users or devices.
  4. Check for client-side credential exposure
    Inspect web browser developer tools (Network/Fission tabs) when using the iSolarCloud web interface. Look for MQTT broker URLs, usernames, passwords, or decryption keys appearing in API responses, JavaScript files, or WebSocket connections.
    Affected if Valid MQTT credentials, broker endpoints, or encryption keys are visible in client-side code or responses.
  5. Verify user isolation on MQTT topics
    Subscribe to a topic belonging to a different user account (e.g., 'device/+/telemetry' or user-specific paths). Compare whether messages from other user accounts are accessible.
    Affected if Messages from other users' devices are reachable with a standard authenticated account.

A user is affected if the iSolarCloud MQTT service is running and allows unrestricted '#' wildcard subscriptions or exposes credentials client-side, enabling cross-user data interception.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement MQTT topic ACLs to restrict users to only their authorized device topics, and review credential/key handling to prevent extraction of valid credentials from the client-side.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29756 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29756 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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