Skip to main content
VulnerabilityPublished Updated

CVE-2025-64385: Circutor TCPRS1plus · Improper Input Validation

Affects Circutor TCPRS1plusSource CVE Database V5

0

Not known to be exploited · CVSS 9.2 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% 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:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Circutor TCPRS1plusAffected
  • =1.0.14
Fixed in–

AI-suggested

1. Immediately implement network segmentation to isolate Circutor TCPRS1plus devices from general enterprise networks and restrict access to trusted management systems only. 2. Employ strict MAC address filtering on network switches and routers to prevent unauthorized devices from spoofing legitimate MAC addresses associated with TCPRS1plus devices. 3. Monitor UDP traffic directed at these devices for anomalous or unexpected configuration packets, using intrusion detection systems (IDS) or network behavior analysis tools. 4. Disable or restrict UDP-based configuration interfaces if possible until a vendor patch is available. 5. Engage with Circutor to obtain firmware updates or patches addressing this vulnerability and apply them promptly once released. 6. Conduct regular audits of device configurations to detect unauthorized changes early. 7. Implement strong physical security controls to prevent local network access that could facilitate MAC spoofing. 8. Educate operational technology (OT) and IT security teams about this vulnerability and the importance of monitoring and controlling device configuration channels.

Description

The equipment initially can be configured using the manufacturer's application, by Wi-Fi, by the web server or with the manufacturer’s software. Using the manufacturer's software, the device can be configured via UDP. Analyzing this communication, it has been observed that any aspect of the initial configuration can be changed by means of the device's MAC without the need for authentication.

References

Community reviews

Loading reviews…