dbcve.org
Dsl 7740c FirmwareOperating system · Dlink

CVE-2025-29514

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-25
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
Incorrect access control in the config.xgi function of D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 allows attackers to download the configuration file via providing a crafted web request.

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 · moderate confidence

The D-Link DSL-7740C router with firmware DSL7740C.V6.TR069.20211230 contains an incorrect access control vulnerability in the config.xgi function. Attackers can craft malicious web requests to download the router's configuration file without authentication, potentially exposing sensitive settings, ISP credentials, and network parameters.

MitigationApply any available firmware update from D-Link; if unavailable, disable remote web management, restrict administrative interface access to trusted networks only, and consider replacing the end-of-life device.

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
Dsl 7740c FirmwareOperating system
Affected:= 6.tr069.20211230

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 the device model
    Check the router label or web interface for the exact model number to confirm it is a D-Link DSL-7740C
    Affected if The device is not a D-Link DSL-7740C (not affected)
  2. Check the firmware version
    Access the router web interface or check via telnet/SSH for the firmware version, looking specifically for version 6.TR069.20211230
    Affected if Firmware version equals 6.TR069.20211230 (vulnerable version)
  3. Test unauthenticated config.xgi access
    From an external or untrusted network perspective, send an HTTP GET request to the config.xgi endpoint (for example: http://<router-ip>/config.xgi?download) without providing any authentication credentials
    Affected if The router returns a configuration file containing ISP credentials, network settings, or administrative passwords without requiring login (vulnerable)
  4. Verify web management exposure
    Confirm whether the router's web management interface (port 80/443) is accessible from untrusted networks or the internet
    Affected if The web interface is exposed to untrusted networks (the attack surface exists)

A user is affected if they have a D-Link DSL-7740C router running firmware version 6.TR069.20211230 and the config.xgi endpoint returns configuration data without authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available firmware update from D-Link; if unavailable, disable remote web management, restrict administrative interface access to trusted networks only, and consider replacing the end-of-life device.

Fix this in Dsl 7740c Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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