CVE-2025-4349
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 vulnerability classified as critical has been found in D-Link DIR-600L up to 2.07B01. This affects the function formSysCmd. The manipulation of the argument host leads to command injection. It is possible to initiate the attack remotely. 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 confidenceCritical command injection vulnerability in D-Link DIR-600L routers (firmware up to 2.07B01). The formSysCmd function improperly handles the 'host' argument, allowing remote attackers to inject and execute arbitrary shell commands on the 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<= 2.07b01CVSS 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.
-
Identify device modelAccess the router's web management interface and check the device information page, or use network discovery to identify the device by its MAC OUI (D-Link) and model name DIR-600L in the device hostname or HTTP response headers.Affected if The device is a D-Link DIR-600L router.
-
Check firmware versionLog into the router web interface and navigate to the Status or System Information page to view the firmware version. Alternatively, check the HTTP response from the router's login page for version strings in the HTML or JavaScript.Affected if The firmware version is 2.07B01 or any version lower than 2.07B01.
-
Verify network exposure of management interfaceDetermine if the router's HTTP/HTTPS management interface (typically ports 80 or 443) is accessible from untrusted networks by scanning external IP addresses or checking firewall rules that allow inbound traffic to the device.Affected if The router's web management interface is exposed to the internet or untrusted networks without proper access controls.
-
Confirm formSysCmd endpoint is accessibleSend an HTTP POST request to /formSysCmd or /cgi-bin/ with the host parameter used in the command injection vector. On an affected device, the endpoint will respond even without authentication.Affected if The formSysCmd endpoint responds to unauthenticated HTTP requests.
A user is affected if they have a D-Link DIR-600L router running firmware version 2.07B01 or lower, with the management interface network-accessible to untrusted parties.
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.
dbcve · scopedThis is an end-of-life device receiving no vendor support. Recommended mitigation is immediate replacement of the affected device or network isolation if replacement is not immediately feasible.
- The D-Link DIR-600L firmware version 2.07b01 and below is end-of-life and no longer supported by D-Link.
- No official firmware patch or security update is available from D-Link for this vulnerability.
- Replace the end-of-life DIR-600L device with a currently supported router model from D-Link or another vendor.
- If replacement is not immediately possible, place the device behind a properly configured firewall and restrict network access to trusted users only.
- Disable any remote management interfaces if not required.
- Monitor the device for any unauthorized access attempts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-4349 — 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-4349 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