CVE-2025-64389: Circutor TCPRS1plus · Cleartext Transmission
Affects Circutor TCPRS1plusSource CVE Database V5
Not known to be exploited · CVSS 8.3 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:L/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Circutor TCPRS1plus | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-64389, European organizations should take the following specific actions: 1) Immediately assess and inventory all Circutor TCPRS1plus devices running version 1.0.14 or affected firmware. 2) Disable any insecure protocols or services on the device’s web server that transmit data in cleartext. 3) If possible, configure the device to use encrypted communication channels such as HTTPS with valid TLS certificates. 4) Implement network segmentation to isolate these devices from general user networks, limiting exposure to potential attackers. 5) Employ network monitoring and intrusion detection systems to detect anomalous traffic or attempts to access the device’s web interface. 6) Engage with Circutor for firmware updates or patches addressing this vulnerability; if none are available, consider compensating controls such as VPN tunnels for management access. 7) Educate users and administrators about the risks of accessing the device’s web interface over untrusted networks. 8) Regularly review device configurations and logs for signs of exploitation attempts. These measures go beyond generic advice by focusing on device-specific controls and network architecture adjustments.
Description
The web server of the device performs exchanges of sensitive information in clear text through an insecure protocol.