dbcve.org
Dwr M961 FirmwareOperating system · Dlink

CVE-2026-1624

HIGH · 8.8 CVSS v3.1 Published 2026-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A security vulnerability has been detected in D-Link DWR-M961 1.1.47. The affected element is an unknown function of the file /boafrm/formLtefotaUpgradeFibocom. Such manipulation of the argument fota_url leads to command injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.

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 confidence

D-Link DWR-M961 router firmware version 1.1.47 contains a command injection vulnerability in the /boafrm/formLtefotaUpgradeFibocom form handler. The fota_url parameter is not properly sanitized before being passed to a system call, allowing an attacker to inject arbitrary OS commands. This can be exploited remotely without authentication.

MitigationUpdate D-Link DWR-M961 to a patched firmware version if available. If no patch exists, restrict administrative interface access to trusted networks only via firewall rules or disable remote management.

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
Dwr M961 FirmwareOperating system
Affected:= 1.1.47

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DWR-M961 firmware version
    Access the router admin web interface and navigate to the Status or System Information page to view the firmware version. Alternatively, check the firmware file name or the administration page for the exact version number.
    Affected if The installed firmware version is exactly 1.1.47.
  2. Verify router model is DWR-M961
    Check the router model identifier in the web interface status page, on the device label, or in the administration/system settings.
    Affected if The device is a D-Link DWR-M961 model.
  3. Check web interface accessibility
    Attempt to access the router web administration interface via HTTP/HTTPS on the LAN or WAN IP address. Look for the /boafrm/formLtefotaUpgradeFibocom endpoint or navigate to the LTE/4G or FOTA upgrade settings page.
    Affected if The router web interface is accessible and the LTE FOTA upgrade functionality is present.
  4. Identify vulnerable parameter handling
    Inspect the web interface for LTE firmware upgrade or FOTA (Firmware Over The Air) configuration options. The vulnerability exists in the fota_url parameter processing within the formLtefotaUpgradeFibocom handler.
    Affected if The router runs firmware 1.1.47 on a DWR-M961 device and the LTE FOTA upgrade web form is present and processes the fota_url parameter without sanitization.

A user is affected if they are running D-Link DWR-M961 firmware version exactly 1.1.47 with the LTE FOTA upgrade web interface accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update D-Link DWR-M961 to a patched firmware version if available. If no patch exists, restrict administrative interface access to trusted networks only via firewall rules or disable remote management.

Recommended fix Moderate confidence

Latest available DWR-M961 firmware from D-Link official support (version higher than 1.1.47)

  1. 1. Visit the official D-Link support page at www.dlink.com and navigate to the DWR-M961 product support section.
  2. 2. Download the latest available firmware version for the DWR-M961 router.
  3. 3. Access the router's web management interface by logging in with administrator credentials.
  4. 4. Navigate to the firmware upgrade section (typically under System or Administration settings).
  5. 5. Upload and apply the latest firmware version, ensuring the device remains powered on throughout the process.
  6. 6. After the firmware update completes, verify the router is functioning normally.
  7. 7. Confirm the vulnerability is resolved by checking that the /boafrm/formLtefotaUpgradeFibocom endpoint no longer allows command injection via the fota_url parameter.
Caveat Firmware updates may reset router configuration to defaults; backup settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dwr M961 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1624 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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