CVE-2026-1596
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 · uneditedA flaw has been found in D-Link DWR-M961 1.1.47. This vulnerability affects the function sub_419920 of the file /boafrm/formLtefotaUpgradeQuectel. This manipulation of the argument fota_url causes command injection. The attack is possible to be carried out remotely. The exploit has been published 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 · moderate confidenceD-Link DWR-M961 router firmware 1.1.47 contains a command injection vulnerability in the web management interface function sub_419920 within /boafrm/formLtefotaUpgradeQuectel. The fota_url parameter is not properly sanitized before being used in a system call, allowing an unauthenticated remote attacker to execute arbitrary commands on the device.
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.1.47CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the firmware versionAccess the router's web management interface and navigate to the firmware or status page to view the current firmware version, or use commands like 'cat /proc/version' or 'nvram get firm_version' if you have CLI access via telnet/SSHAffected if The installed firmware version is exactly 1.1.47 (no other versions are listed as affected)
-
Confirm the vulnerable CGI endpoint existsIf you have filesystem access (via telnet/SSH or by extracting firmware), check for the existence of the binary or script handling /boafrm/formLtefotaUpgradeQuectel, typically found in the web server root directoryAffected if The file handling the formLtefotaUpgradeQuectel function exists in the firmware filesystem
-
Verify web management interface is accessibleAttempt to access the router's web interface on the default HTTP port (80) or HTTPS port (443) from the network where the device is deployedAffected if The web management interface responds to HTTP/HTTPS requests
-
Determine if remote administration is enabledIn the router's web UI, check the administrative settings or remote management section to see if remote access (WAN-side) is enabled, or review firewall rules that allow external access to ports 80/443Affected if Remote administration is enabled and the web interface is reachable from untrusted networks (WAN)
A user is affected if the device runs firmware version 1.1.47 and has its web management interface accessible, particularly from untrusted networks, enabling unauthenticated attackers to inject commands via the fota_url parameter.
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 update when available; immediately restrict access to the router's web management interface from untrusted networks using firewall rules or by disabling remote administration.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1596 — 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-2026-1596 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