CVE-2025-11408
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 · uneditedA security vulnerability has been detected in D-Link DI-7001 MINI 24.04.18B1. The affected element is an unknown function of the file /dbsrv.asp. Such manipulation of the argument str leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed publicly 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 · moderate confidenceBuffer overflow vulnerability in D-Link DI-7001 MINI router firmware 24.04.18B1 in the /dbsrv.asp file. The 'str' argument is not properly validated before use, allowing an attacker to overflow a buffer via crafted input. This is a critical remote code execution vulnerability.
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= 24.04.18b1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is D-Link DI-7001 MINIAccess the router's web interface at its LAN IP (typically 192.168.0.1 or 192.168.1.1) and look for the model name in the status or system information page, or physically inspect the device label.Affected if Device model is not D-Link DI-7001 MINI
-
Identify installed firmware versionIn the router web interface, navigate to the Status or System Settings page and locate the firmware version field. The version number is typically displayed as something like '24.04.18B1' or similar.Affected if Firmware version equals 24.04.18B1
-
Verify /dbsrv.asp endpoint is presentAccess the URL '/dbsrv.asp' on the router's web interface (e.g., http://<router-ip>/dbsrv.asp) using a web browser or curl command. Check if the page loads or returns a response.Affected if The /dbsrv.asp endpoint responds or exists on the device
-
Check if remote management is exposedIn the router web interface, look under sections named 'Remote Management', 'Administration', 'System Management', or 'Access Control' for settings that allow WAN/remote access to the web interface. Note whether 'Enable Remote Management' or similar options are checked or set to allow external access.Affected if Remote management or WAN access to the web interface is enabled
You are affected if you have a D-Link DI-7001 MINI router running firmware version 24.04.18B1 with the /dbsrv.asp endpoint accessible, especially if remote management is enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patch if available; otherwise, restrict network access to the device's web management interface to trusted IPs only. Consider replacing the end-of-life device if no firmware update is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-11408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11408 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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