CVE-2025-41708: Bender CC612 · Cleartext Transmission
Affects Bender CC612Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bender CC612 | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability effectively, organizations should immediately assess their deployment of Bender CC612 devices and verify the configuration of the web interface. The primary recommendation is to enforce the use of HTTPS by configuring the device to disable HTTP access and enable secure TLS-based communication. If the device firmware does not support HTTPS or secure configuration options, organizations should contact the vendor for patches or updated firmware that address this issue. Network-level mitigations include isolating the device on a dedicated VLAN or subnet with strict access controls to limit exposure to only trusted users and systems. Implementing network monitoring and intrusion detection systems to detect anomalous traffic patterns can help identify exploitation attempts. Additionally, organizations should conduct regular security audits and penetration tests focusing on network segmentation and device configurations. Educating staff about the risks of unsecured device interfaces and enforcing strong network access policies will further reduce the attack surface. Finally, organizations should maintain an inventory of affected devices and track vendor advisories for any forthcoming patches or updates.
Description
Due to an unsecure default configuration HTTP is used instead of HTTPS for the web interface. An unauthenticated attacker on the same network could exploit this to learn sensitive data during transmission.