CVE-2025-45986
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 werediscovered to contain a command injection vulnerability via the mac parameter in the bs_SetMacBlack 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 confidenceMultiple Blink router models contain a command injection vulnerability in the bs_SetMacBlack function where the mac parameter is not properly sanitized, allowing remote attackers to execute arbitrary operating system commands on the affected devices.
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= 1.0.5= 1.2.3= 2.4.9= 1.0.4= 4.0.0= 1.2.7= 1.0.0= 1.2.8CVSS 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 modelCheck the device label on the router or log into the web management interface and look for the model number displayed on the status or device info pageAffected if The model matches one of the eight affected models: BL-WR9000, BL-AC2100_AZ3, BL-X10_AC8, BL-LTE300, BL-F1200_AT1, BL-X26_AC8, BLAC450M_AE4, or BL-X26_DA3
-
Check installed firmware versionLog into the router web interface and navigate to Status or System settings to view the firmware version. Alternatively, check the version via CLI if SSH/Telnet access is availableAffected if The firmware version matches exactly one of the affected versions: 1.0.5 (BL-X10_AC8), 1.2.3 (BL-LTE300), 2.4.9 (BL-WR9000), 1.0.4 (BL-AC2100_AZ3), 4.0.0 (BLAC450M_AE4), 1.2.7 (BL-X26_DA3), 1.0.0 (BL-F1200_AT1), or 1.2.8 (BL-X26_AC8)
-
Verify web management interface is accessibleAttempt to access the router web interface from the network. Check if HTTP/HTTPS ports (typically 80 or 443) are open and reachable on the router IPAffected if The web management interface is reachable from an untrusted network (such as the internet or a guest network)
-
Check if MAC filtering feature is accessibleLog into the web interface and navigate to the MAC filtering or access control section. Look for a feature called bs_SetMacBlack or MAC Blacklist/Blacklist functionalityAffected if The MAC filtering feature with the bs_SetMacBlack function is present and accessible in the web interface
A user is affected if they own one of the eight listed router models with the exact firmware version specified, have the web management interface exposed, and can access the MAC filtering feature in the web interface.
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 dataApply vendor firmware updates when available; until then, restrict network access to router management interfaces and implement input validation on the mac parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-45986 — 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-45986 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