CVE-2025-7770: Tigo Energy Cloud Connect Advanced · PRNG
Affects Tigo Energy Cloud Connect AdvancedSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% 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:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Tigo Energy Cloud Connect Advanced | Affected
| Fixed in– |
AI-suggested
2) Implement network segmentation to isolate CCA devices from broader enterprise networks, limiting potential lateral movement. 3) Employ strict access controls and monitoring on the API endpoints, including anomaly detection to identify unusual session ID patterns or unauthorized command usage. 4) Where possible, deploy compensating controls such as VPNs or IP whitelisting to restrict remote API access to trusted sources only. 5) Conduct regular security assessments and penetration testing focusing on solar infrastructure components. 6) Advocate for or implement multi-factor authentication and enhanced session management mechanisms once vendor support is available. 7) Maintain comprehensive logging and incident response plans tailored to industrial control systems and energy infrastructure. These steps go beyond generic advice by focusing on compensating controls and proactive network architecture adjustments pending vendor patches.
Description
Tigo Energy's CCA device is vulnerable to insecure session ID generation in their remote API. The session IDs are generated using a predictable method based on the current timestamp, allowing attackers to recreate valid session IDs. When combined with the ability to circumvent session ID requirements for certain commands, this enables unauthorized access to sensitive device functions on connected solar optimization systems.