DialinkApplication · Deltaww

CVE-2025-58320

HIGH · 7.3 CVSS v3.1 Developing Published 2025-09-11
Fix available
A fix is available. Upgrade to 1.8.0.0 or later.
See remediation →
82/100
Remediation priority · High
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
Delta Electronics DIALink has an Directory Traversal Authentication Bypass 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 · low confidence

Delta Electronics DIALink contains a combined vulnerability allowing directory traversal and authentication bypass. This enables remote attackers to access files outside the intended web root directory without proper authentication credentials, potentially exposing sensitive system files or configuration data.

MitigationApply vendor patches when available; implement strict input validation on file path parameters to prevent traversal sequences; review and harden authentication mechanisms; restrict file system access permissions.

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
DialinkApplication
Affected:< 1.8.0.0

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 DIALink installation version
    Locate the DIALink application and retrieve its version number through the software's about page, installer metadata, or version file within the installation directory
    Affected if The installed version is below 1.8.0.0
  2. Verify web interface accessibility
    Determine if the DIALink web interface is exposed to network access by checking network listener configurations, firewall rules, or by attempting to reach the web service endpoint
    Affected if The web interface is reachable from network segments beyond the intended local administration scope
  3. Confirm authentication is enforced on file operations
    Test file access endpoints by sending requests without valid authentication credentials to determine if the system permits unauthenticated access
    Affected if The application allows file operations or file downloads without requiring valid authentication tokens or session credentials
  4. Check for directory traversal protection
    Submit requests containing path traversal sequences (such as ../) to file-related API endpoints or parameters to observe if the application permits escaping the intended web root directory
    Affected if The application allows path traversal sequences to access files or directories outside the expected web root hierarchy

Your environment is affected if DIALink version is below 1.8.0.0 AND the web interface is accessible with unauthenticated traversal requests succeeding.

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
Upgrade available Upgrade to 1.8.0.0 or later
Fixed in 1.8.0.0
Interim mitigation

Apply vendor patches when available; implement strict input validation on file path parameters to prevent traversal sequences; review and harden authentication mechanisms; restrict file system access permissions.

Recommended fix Moderate confidence

1.8.0.0

  1. Obtain the latest version of DIALink (1.8.0.0) from the official Delta Electronics download center at filecenter.deltaww.com
  2. Back up current DIALink configuration and data before upgrading
  3. Install DIALink version 1.8.0.0 following the standard installation procedures provided in the product documentation
  4. Verify the installation was successful and confirm the version number
  5. Test that the application functions normally after the upgrade

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

Fix this in Dialink 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 the upgrade done

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-58320 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58320 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