dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70231

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
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
D-Link DIR-513 version 1.10 contains a critical-level vulnerability. When processing POST requests related to verification codes in /goform/formLogin, it enters /goform/getAuthCode but fails to filter the value of the FILECODE parameter, resulting in a path traversal vulnerability.

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 DIR-513 v1.10 has a path traversal vulnerability in the web authentication flow. The /goform/formLogin and /goform/getAuthCode endpoints process the FILECODE parameter from POST requests without proper input filtering, allowing attackers to access arbitrary files on the device filesystem via path traversal sequences (e.g., ../../).

MitigationApply vendor firmware update if available; otherwise isolate device on restricted network segment or implement WAF rules to filter path traversal patterns in requests to /goform/* endpoints. Consider device replacement if EOL.

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 513 FirmwareOperating system
Affected:= 1.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. Confirm device model is D-Link DIR-513
    Access the device web interface or check the device label/marketing to verify the exact model number. Alternatively, inspect DHCP lease tables or network scans for device identification.
    Affected if Device is not a D-Link DIR-513 model
  2. Identify installed firmware version
    Log into the router web interface and navigate to the Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the device release notes or backup configuration files for version strings.
    Affected if Firmware version is 1.10
  3. Verify web service is accessible
    Attempt to access the device web interface via HTTP/HTTPS on the default LAN IP (commonly 192.168.0.1) or the configured management IP address.
    Affected if Web interface is not reachable or responds with 404 errors for all endpoints
  4. Check for affected endpoints
    Send a POST request to /goform/formLogin or /goform/getAuthCode with any payload and observe the response. Use a tool like curl: curl -X POST http://<device_ip>/goform/formLogin -d "test=value"
    Affected if Endpoints return a response indicating the path traversal vulnerability is present (no error or unexpected file content in response)
  5. Inspect for path traversal vulnerability
    Send a POST request with a FILECODE parameter containing path traversal sequences (e.g., ../../etc/passwd or ../../proc/version) to /goform/formLogin or /goform/getAuthCode. Analyze if arbitrary file contents are returned.
    Affected if FILECODE parameter accepts and processes path traversal sequences, returning file contents outside the intended directory

A user is affected if they are running D-Link DIR-513 firmware version 1.10 and the web interface responds to the /goform/formLogin or /goform/getAuthCode endpoints with path traversal behavior in the FILECODE parameter.

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 vendor firmware update if available; otherwise isolate device on restricted network segment or implement WAF rules to filter path traversal patterns in requests to /goform/* endpoints. Consider device replacement if EOL.

Fix this in Dir 513 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-70231 — 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-70231 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