dbcve.org
Dir 825 FirmwareOperating system · Dlink

CVE-2025-8949

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
A vulnerability was identified in D-Link DIR-825 2.10. Affected by this vulnerability is the function get_ping_app_stat of the file ping_response.cgi of the component httpd. The manipulation of the argument ping_ipaddr leads to stack-based buffer overflow. 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 stack-based buffer overflow vulnerability exists in D-Link DIR-825 router firmware version 2.10 within the httpd web server's ping_response.cgi script. The get_ping_app_stat function fails to properly validate the length of the ping_ipaddr argument before copying it to a fixed-size stack buffer, allowing remote attackers to potentially overwrite return addresses and execute arbitrary code.

MitigationThis vulnerability has no vendor patch as the affected product is end-of-life. Immediate mitigation requires isolating the device on a restricted network segment, disabling remote WAN management, and planning for hardware replacement with a supported model.

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 825 FirmwareOperating system
Affected:= 2.10

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 device model
    Check the device label, web interface system info page, or SSH/console output for the exact model number (DIR-825)
    Affected if Device is NOT a D-Link DIR-825 - not affected
  2. Check firmware version
    Access the router's web interface (typically 192.168.0.1), navigate to Status or System section, and record the firmware version; alternatively, check via SSH/console if available
    Affected if Firmware version is NOT 2.10 - not affected
  3. Verify ping_response.cgi is accessible
    Attempt to access http://<router-ip>/ping_response.cgi via HTTP or HTTPS (note: authentication may be required)
    Affected if Cannot verify access - manual investigation needed; if accessible and firmware is 2.10, likely affected
  4. Confirm ping functionality is enabled
    Check router web interface for ping/ diagnostics settings under Tools, System, or Administration sections; or observe if ping requests to the router are responded to
    Affected if Ping functionality is disabled - risk reduced but CGI may still be vulnerable if accessed directly

If the device is a D-Link DIR-825 running firmware version 2.10 and the ping_response.cgi endpoint is accessible, the environment is affected by this vulnerability.

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

This vulnerability has no vendor patch as the affected product is end-of-life. Immediate mitigation requires isolating the device on a restricted network segment, disabling remote WAN management, and planning for hardware replacement with a supported model.

Recommended fix High confidence
  1. 1. Replace the D-Link DIR-825 with a currently supported router from D-Link or another vendor.
  2. 2. If immediate replacement is not possible, isolate the device on a restricted network segment with firewall rules blocking external access to the httpd service (port 80/443).
  3. 3. Disable the ping functionality on the device if possible through administrative interface.
  4. 4. Monitor for any unauthorized access attempts targeting the ping_response.cgi endpoint.
Caveat The DIR-825 is end-of-life and no longer receives security updates from D-Link; device replacement is required

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

Fix this in Dir 825 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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