CVE-2025-45985: Command Injection
Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 6.8% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Jun 2025
Detectable: evidence found.
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
AI-suggested
1. Immediate network segmentation: Isolate affected Blink routers from critical internal networks to limit potential lateral movement if compromised. 2. Restrict management interface access: Limit router management interfaces to trusted IP addresses and disable remote management if not required. 3. Monitor network traffic for anomalies: Deploy network intrusion detection systems (NIDS) to detect unusual command execution patterns or unexpected outbound connections originating from routers. 4. Firmware verification and update: Regularly check Blink's official channels for firmware updates addressing CVE-2025-45985 and apply patches promptly once available. 5. Disable unnecessary services: If possible, disable or restrict the functionality related to SSID hiding or the bs_SetSSIDHide function to reduce attack surface. 6. Implement strong authentication: Enforce strong passwords and, if supported, multi-factor authentication for router management access. 7. Conduct internal audits: Review router configurations and logs for signs of exploitation or unauthorized changes. 8. Vendor engagement: Engage with Blink support or distributors to obtain timelines for patches and request mitigation guidance specific to affected models. These steps go beyond generic advice by focusing on network architecture adjustments, active monitoring, and vendor interaction tailored to the specific vulnerability and device models.
Description
Blink routers BL-WR9000 V2.4.9 , BL-AC2100_AZ3 V1.0.4, BL-X10_AC8 v1.0.5 , BL-LTE300 v1.2.3, BL-F1200_AT1 v1.0.0, BL-X26_AC8 v1.2.8, BLAC450M_AE4 v4.0.0 and BL-X26_DA3 v1.2.7 were discovered to contain a command injection vulnerability via the bs_SetSSIDHide function.