dbcve.org
Dir 878 FirmwareOperating system · Dlink

CVE-2022-26670

HIGH · 8.8 CVSS v3.1 Published 2022-04-07
Fix available
A fix is available. Upgrade to after 1.20b05 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
D-Link DIR-878 has inadequate filtering for special characters in the webpage input field. An unauthenticated LAN attacker can perform command injection attack to execute arbitrary system commands to control the system or disrupt service.

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

The D-Link DIR-878 router contains a command injection vulnerability due to inadequate filtering of special characters in a webpage input field. An unauthenticated attacker on the LAN can inject arbitrary system commands through this input field, achieving remote code execution with the privileges of the affected service.

MitigationApply the vendor-supplied firmware update when available. Until then, isolate affected devices on restricted network segments and limit LAN access to trusted users only.

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
Dir 878 FirmwareOperating system
Affected:<= 1.20b05

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

CVSS:3.1/AV:A/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 checks

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

  1. Identify the router model
    Check the device label or admin interface to confirm the model is D-Link DIR-878
    Affected if Device is a D-Link DIR-878 router
  2. Check the installed firmware version
    Access the router web admin interface (typically at 192.168.0.1) and navigate to the Status or Management page to view the firmware version, or use the command 'cat /proc/version' or '固件版本' page if you have telnet/SSH access
    Affected if Firmware version is 1.20b05 or lower
  3. Verify the device is network accessible
    Confirm the router is powered on and reachable on the LAN network
    Affected if Router is accessible on the local network (vulnerable input field requires LAN access)
  4. Confirm the web management interface is reachable
    Attempt to access the router login page via HTTP on the LAN IP address (commonly 192.168.0.1)
    Affected if Web interface is accessible from the LAN side

The environment is affected if the device is a D-Link DIR-878 router running firmware version 1.20b05 or lower and the web management interface is accessible from the LAN.

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
Upgrade available Upgrade to a release after 1.20b05
Interim mitigation

Apply the vendor-supplied firmware update when available. Until then, isolate affected devices on restricted network segments and limit LAN access to trusted users only.

Recommended fix Moderate confidence

D-Link DIR-878 firmware version 1.21 or later (verify latest version from official D-Link support)

  1. 1. Identify the current firmware version of the D-Link DIR-878 router by accessing the web management interface and navigating to the Status or System section.
  2. 2. Navigate to the firmware upgrade or maintenance section of the router's web interface.
  3. 3. Download the latest firmware version from the official D-Link support website (support.dlink.com) specifically for the DIR-878 model.
  4. 4. Upload and apply the new firmware version through the router's web management interface, following the on-screen instructions.
  5. 5. After the firmware upgrade completes, verify that the router is functioning normally and confirm the new firmware version is installed.
  6. 6. Ensure the router is restarted and all network connectivity is restored.
Caveat Firmware upgrades may reset some custom configurations; backup settings before upgrading if possible

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

Fix this in Dir 878 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26670 — 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-2022-26670 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