dbcve.org
Dir X1860 FirmwareOperating system · Dlink

CVE-2021-46353

MEDIUM · 5.3 CVSS v3.1 Published 2022-03-04
Fix available
A fix is available. Upgrade to after 1.03 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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
An information disclosure in web interface in D-Link DIR-X1860 before 1.03 RevA1 allows a remote unauthenticated attacker to send a specially crafted HTTP request and gain knowledge of different absolute paths that are being used by the web application.

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

A detailed technical summary for this CVE is being prepared.

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 X1860 FirmwareOperating system
Affected:<= 1.03

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.03
Vendor patch supportannouncement.us.dlink.com →
Recommended fix High confidence

DIR-X1860 firmware 1.03 RevA1 or later

  1. 1. Access the D-Link DIR-X1860 router web interface by navigating to the device's IP address (typically 192.168.0.1 or 192.168.1.1)
  2. 2. Log in with administrator credentials
  3. 3. Navigate to the 'Management' or 'Settings' section
  4. 4. Locate the 'Firmware Upgrade' or 'Router Update' option
  5. 5. Download the latest firmware version (1.03 RevA1 or later) from the official D-Link support site: https://supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10283
  6. 6. In the web interface, select the downloaded firmware file and initiate the upgrade
  7. 7. Wait for the firmware upload and installation to complete - do not power off the device during this process
  8. 8. After the router restarts, log back into the web interface and verify the firmware version under 'Status' or 'Device Info'
Caveat Firmware upgrades may reset some custom configurations; backup current settings before upgrading if possible

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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