dbcve.org
Dir 816 FirmwareOperating system · Dlink

CVE-2025-1392

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 vulnerability has been found in D-Link DIR-816 1.01TO and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /cgi-bin/webproc?getpage=html/index.html&var:menu=24gwlan&var:page=24G_basic. The manipulation of the argument SSID leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

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

A reflected cross-site scripting (XSS) vulnerability exists in the D-Link DIR-816 1.01TO router's web management interface. The SSID parameter in the /cgi-bin/webproc CGI script (specifically when handling the 24G_basic page) does not properly sanitize user input, allowing remote attackers to inject malicious JavaScript code via the SSID argument.

MitigationSince this product is end-of-life and no longer supported by D-Link, the recommended remediation is to replace the affected device with a currently supported model. If immediate replacement is not feasible, network segmentation can limit exposure to the management interface.

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 816 FirmwareOperating system
Affected:= 1.01to

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 device model is D-Link DIR-816
    Access the router web interface (typically at 192.168.0.1) and navigate to Status or Device Info page to verify the model number displays as DIR-816. Alternatively, check the physical device label on the router chassis.
    Affected if The device model is not D-Link DIR-816, then this specific CVE does not apply.
  2. Check firmware version is 1.01TO
    In the router web interface, go to Status or System Settings and locate the Firmware Version field. Verify it displays exactly 1.01TO (or 1.01to). Some interfaces show this under Maintenance > Firmware Upgrade or Status > Device Information.
    Affected if The firmware version is anything other than 1.01TO, the specific vulnerability version is not present.
  3. Verify web management interface is accessible
    Attempt to reach the router's web interface at its default IP address (commonly 192.168.0.1 or 192.168.1.1) using a web browser. Confirm the login page or management interface loads successfully.
    Affected if The web management interface is not accessible (disabled or blocked), the attack surface for this XSS is not present.
  4. Confirm vulnerable CGI endpoint exists
    Access the router web interface and navigate to Wireless Settings (the 24G_basic page typically contains 2.4GHz Wi-Fi SSID configuration). Verify the page loads without errors at /cgi-bin/webproc or through the wireless configuration menu.
    Affected if The 24G wireless settings page is not accessible or the webproc CGI interface is not present, the specific XSS vector does not exist.

If the device is confirmed to be a D-Link DIR-816 running firmware version 1.01TO with the web management interface accessible and the wireless settings page functional, the environment is affected by this CVE.

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

Since this product is end-of-life and no longer supported by D-Link, the recommended remediation is to replace the affected device with a currently supported model. If immediate replacement is not feasible, network segmentation can limit exposure to the management interface.

Recommended fix High confidence
  1. 1. Confirm the device has reached end-of-life (EOL) status as explicitly stated in the vulnerability description
  2. 2. Since D-Link no longer supports this device, no firmware patch will be released
  3. 3. Replace the affected D-Link DIR-816 device with a currently supported router model from D-Link or another vendor
  4. 4. If immediate replacement is not possible, implement network-level mitigations: configure a behind-NAT deployment, disable remote management interfaces exposed to the internet, and consider using a web application firewall (WAF) to filter XSS payloads
Caveat Device is end-of-life with no vendor support; replacement is the only secure path forward

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

Fix this in Dir 816 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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