CVE-2025-45985
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBlink 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCommand injection vulnerability in the bs_SetSSIDHide function across multiple Blink router models allows remote attackers to inject and execute arbitrary operating system commands on affected devices via unsanitized input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.4.9= 1.0.4= 1.0.5= 1.2.3= 1.0.0= 1.2.8= 4.0.0= 1.2.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLog into the router web interface (typically 192.168.1.1 or 192.168.0.1) and check the Device Info or Status page for the exact model name. Alternatively, check the device label or packaging.Affected if Model matches any of: Bl Wr9000, Bl Ac2100 Az3, Bl X10 Ac8, Bl Lte300, Bl F1200 At1, Bl X26 Ac8, Blac450m Ae4, or Bl X26 Da3
-
Check firmware versionIn the router web interface, navigate to System Settings or Firmware Upgrade page and locate the firmware version number. Compare it exactly to the affected versions: 2.4.9 (Wr9000), 1.0.4 (Ac2100 Az3), 1.0.5 (X10 Ac8), 1.2.3 (Lte300), 1.0.0 (F1200 At1), 1.2.8 (X26 Ac8), 4.0.0 (ac450m Ae4), or 1.2.7 (X26 Da3).Affected if Firmware version exactly matches one of the listed affected versions for your model
-
Verify if remote web management is enabledIn the router web interface, go to Remote Management or Access Control settings. Check if Remote Web Management, Remote Administration, or similar option is turned ON, and note the allowed IP range if any.Affected if Remote management is enabled and accessible from external networks (WAN side)
-
Locate the SSID Hide settingNavigate to Wireless or WiFi settings in the router web interface. Look for an option to Hide SSID, Broadcast SSID, or similar wireless visibility setting. The vulnerable function bs_SetSSIDHide handles this feature.Affected if The Hide SSID or similar wireless visibility feature exists and is configurable via the web interface
Your device is affected if it is one of the listed B Link Blink models running the exact firmware version AND the web management interface is accessible (especially from WAN), allowing unsanitized input to the SSID hide configuration function.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to router management interfaces, disable remote administration if possible, and monitor for indicators of compromise until vendor-provided firmware patches are available.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-45985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-45985 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data