dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-70796

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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
An unauthenticated path traversal vulnerability exists in the web management interface of WTI (Wireless Technology, Inc.) version 3.5.0.r 2024/05/24 00:00:00. An unauthenticated attacker can craft malicious HTTP requests containing traversal sequences to access files outside of the intended web root directory. This may allow disclosure of sensitive system files and configuration data

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

WTI web management interface version 3.5.0.r contains an unauthenticated path traversal vulnerability. Attackers can send HTTP requests with '..' traversal sequences to escape the web root and read arbitrary files on the underlying filesystem, exposing sensitive system files and configuration data.

MitigationApply vendor patch when available. Until then, restrict network access to the web management interface to trusted IPs only, and implement strict input validation to reject path traversal sequences in all file path parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Availability
None

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

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 if WTI web management interface is present
    Check for running web services on common WTI ports (typically port 80/443 or vendor-specified ports). Use 'netstat -tulpn' or 'ss -tulpn' to list listening services, or review network scans for WTI-specific HTTP responses.
    Affected if The WTI web management interface service is running and accessible on the network.
  2. Determine the installed version of WTI web interface
    Check the version banner by accessing the HTTP response headers or login page of the WTI web interface. Version information may also be found in the web server configuration files or the WTI device management interface.
    Affected if The installed version is 3.5.0.r (the specifically affected version) or falls within the version range containing this release.
  3. Verify network accessibility of the web management interface
    Check firewall rules, network ACLs, or cloud security groups to determine if the web management interface port is exposed to untrusted networks. Review whether the interface is bound to 0.0.0.0 or an external-facing IP.
    Affected if The web management interface is reachable from untrusted network segments or the public internet.
  4. Inspect logs for path traversal attempts
    Review web server access logs and WTI system logs for requests containing '..' sequences, such as '../etc/passwd' or '..\..\Windows\win.ini'. Check for any failed file access attempts that escaped the web root.
    Affected if There are historical or ongoing path traversal requests in the logs, indicating potential exploitation attempts.
  5. Check for input validation on file path parameters
    Test the web interface by submitting requests with '..' sequences in any file path parameters (if testing in a non-production environment). Review application configuration for any existing input validation or WAF rules blocking traversal patterns.
    Affected if No input validation exists to filter or block path traversal sequences in HTTP requests.

A user is affected if they have WTI web management interface version 3.5.0.r running and the interface is accessible to network attackers without input validation blocking '..' traversal sequences.

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 patch when available. Until then, restrict network access to the web management interface to trusted IPs only, and implement strict input validation to reject path traversal sequences in all file path parameters.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing5.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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