dbcve.org
Di 7300g\+ FirmwareOperating system · Dlink

CVE-2025-6897

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-30
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
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 classified as critical was found in D-Link DI-7300G+ 19.12.25A1. Affected by this vulnerability is an unknown functionality of the file httpd_debug.asp. The manipulation of the argument Time leads to os command injection. The exploit has been disclosed to the public 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 · high confidence

D-Link DI-7300G+ router firmware 19.12.25A1 contains a critical OS command injection vulnerability in the httpd_debug.asp web interface. The 'Time' parameter is not properly sanitized before being passed to system shell commands, allowing remote attackers to execute arbitrary OS commands with elevated privileges.

MitigationApply any available vendor firmware update from D-Link. If no patch exists, isolate the device behind a firewall with no external access, or replace the device with a supported model. Validate the fix by testing that command injection payloads in the Time parameter are no longer executed.

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
Di 7300g\+ FirmwareOperating system
Affected:= 19.12.25a1

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. Confirm device model
    Access the router web interface or check the device label to verify the model is D-Link DI-7300G+. This is typically found on the device itself or in the admin panel under Status or System Information.
    Affected if The device is a D-Link DI-7300G+ router
  2. Check installed firmware version
    Log into the router admin panel and navigate to Status or System Information page to view the firmware version. Alternatively, check the httpd banner or upgrade page if accessible.
    Affected if The firmware version is exactly 19.12.25A1
  3. Verify httpd_debug.asp is accessible
    Attempt to access http://<router-ip>/httpd_debug.asp or http://<router-ip>/asp/httpd_debug.asp in a web browser. Check if the page loads or returns any response.
    Affected if The httpd_debug.asp page is reachable and responds to requests
  4. Check if Time parameter accepts input
    Submit a request to the httpd_debug.asp page with a test value in the Time parameter (e.g., via query string or form submission). Observe whether the input is reflected in the response or processed by the application.
    Affected if The Time parameter on httpd_debug.asp accepts and processes user input without sanitization

The device is affected if it is a D-Link DI-7300G+ running firmware 19.12.25A1 and the httpd_debug.asp interface with the Time parameter is accessible.

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

Apply any available vendor firmware update from D-Link. If no patch exists, isolate the device behind a firewall with no external access, or replace the device with a supported model. Validate the fix by testing that command injection payloads in the Time parameter are no longer executed.

Recommended fix Moderate confidence
  1. Isolate the affected D-Link DI-7300G+ device from the network to reduce exposure
  2. Disable remote management interfaces if not absolutely necessary
  3. If the device is end-of-life (no longer supported by D-Link), replace it with a currently-supported router
  4. Implement network segmentation to limit the impact of potential compromise
  5. Monitor for indicators of compromise since the exploit is publicly disclosed
Caveat The DI-7300G+ appears to be a legacy product likely at end-of-life with no available firmware updates; replacement is recommended

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

Fix this in Di 7300g\+ Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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