Skip to main content
CVE-2025-7769VulnerabilityPublished

CVE-2025-7769: Tigo Energy Cloud Connect Advanced · Command Injection

Affects Tigo Energy Cloud Connect AdvancedSource CVE Database V5

0

Not known to be exploited · public exploit available (Exploit-DB) · 19% EPSS · CVSS 8.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
19.0% chance of exploitation in 30 days – higher than 97% 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:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by icscert

    , 20 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 5 minutes after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    Tigo Energy Cloud Connect Advanced (CCA) 4.0.1 - Command Injection

    , 5 days after disclosure

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-25.

What to do

Affected software

ProductAffectedFixed in
Tigo Energy Cloud Connect AdvancedAffected
  • =0
Fixed in–

AI-suggested

Immediate mitigation steps include changing default credentials on all affected devices to strong, unique passwords to prevent unauthorized access. Network segmentation should be enforced to isolate CCA devices from general IT networks and limit exposure to untrusted networks. Implement strict firewall rules to restrict access to the /cgi-bin/mobile_api endpoint, allowing only trusted management systems. Monitoring and logging of device access and command execution should be enhanced to detect anomalous activities indicative of exploitation attempts. Until a vendor patch is released, consider disabling or restricting the DEVICE_PING command if feasible. Organizations should engage with Tigo Energy for updates on patches or firmware upgrades addressing this vulnerability. Additionally, conducting regular vulnerability assessments and penetration tests on energy management infrastructure can help identify and remediate similar issues proactively.

Description

Tigo Energy's CCA is vulnerable to a command injection vulnerability in the /cgi-bin/mobile_api endpoint when the DEVICE_PING command is called, allowing remote code execution due to improper handling of user input. When used with default credentials, this enables attackers to execute arbitrary commands on the device that could cause potential unauthorized access, service disruption, and data exposure.

References

Community reviews

Loading reviews…