CVE-2026-71954: D-Link DWR-M961 Command Injection via /boafrm/formL2tpv3ConfigSetup
D-Link DWR-M961 devices with hardware version C1 and firmware version before 1.1.5_C1_202607071108 contain a command injection vulnerability in the /boafrm/formL2tpv3ConfigSetup interface. A remote attacker can inject arbitrary malicious commands into the tunnelid and sessionid fields, resulting in command execution with root privileges.
Security readout for executives and security teams
Plain-English summary
A flaw in certain D-Link DWR-M961 routers can let a remote, unauthenticated attacker run operating-system commands as root. Successful compromise could expose traffic and credentials, change router settings, disrupt connectivity, or provide a foothold into connected networks. The issue is limited to hardware revision C1 running firmware older than the vendor-identified fixed version.
Executive priority
Treat internet-reachable affected routers as an immediate remediation priority because compromise requires no credentials and grants root-level control. Update or isolate them urgently. For internally restricted devices, schedule accelerated remediation and verify access controls rather than deferring solely because active exploitation is not documented.
Technical view
CVE-2026-71954 is CWE-78 command injection in /boafrm/formL2tpv3ConfigSetup. Unsafely handled tunnelid and sessionid values can reach command execution with root privileges. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
DWR-M961 hardware revision C1 devices running firmware earlier than 1.1.5_C1_202607071108 are affected. Risk is greatest where the management interface is reachable from the internet or untrusted networks. The bundle does not establish how commonly that interface is exposed.
Exploitation context
The supplied record supports remote, unauthenticated root command execution. It does not provide evidence of active exploitation, and the CVE is not identified as being in KEV. Absence from KEV does not prove exploitation is not occurring; prioritize based on exposure and impact.
Researcher notes
The affected request handler and injectable fields are identified, but the bundle does not describe vulnerable parsing logic, affected firmware ranges beyond the stated cutoff, detection indicators, or observed campaigns. Validation should remain version- and exposure-based; avoid sending injection probes to production devices.
Mitigation direction
Inventory DWR-M961 routers and confirm each device's hardware revision and firmware version.
Upgrade affected C1 devices to firmware 1.1.5_C1_202607071108 or later using D-Link guidance.
Restrict management access to trusted administrative networks and block exposure from the internet.
Review D-Link's advisory for installation requirements, supported releases, and any additional mitigations.
Isolate or replace devices that cannot be promptly updated.
Validation and detection
Verify the hardware label or management interface identifies revision C1.
Record the installed firmware and compare it with 1.1.5_C1_202607071108.
Confirm the management interface is inaccessible from internet and untrusted network segments.
After upgrading, verify the reported firmware version and normal routing operation.
Review device and perimeter logs for unexpected administrative requests or configuration changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.