dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-67115

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A path traversal vulnerability in /ftl/web/setup.cgi in Small Cell Sercomm SCE4255W (FreedomFi Englewood) firmware before DG3934v3@2308041842 allows remote authenticated users to read arbitrary files from the filesystem via crafted values in the log_type parameter to /logsave.htm.

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

A path traversal vulnerability in the web interface (setup.cgi) of Small Cell Sercomm SCE4255W devices allows authenticated users to read arbitrary filesystem files by manipulating the log_type parameter on /logsave.htm with directory traversal sequences (e.g., ../../../etc/passwd). The vulnerability exists in firmware versions prior to DG3934v3@2308041842.

MitigationApply vendor firmware update DG3934v3@2308041842 or later. Until patched, restrict web interface access to trusted authenticated users only and monitor logs for traversal patterns.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm device model is Sercomm SCE4255W
    Access the device web interface or check device documentation/labels to verify the exact model number is Small Cell Sercomm SCE4255W
    Affected if Device model is not SCE4255W
  2. Check installed firmware version
    Log into the device web interface and navigate to the firmware/version information page, or check via CLI if available. Look for a version string such as DG3934v3@2308041842 or similar
    Affected if Firmware version is present and is earlier than DG3934v3@2308041842 (e.g., older DG3934 versions or any version without this date code)
  3. Verify web interface is accessible
    Attempt to reach the device IP address via HTTP/HTTPS to confirm the web interface (setup.cgi, logsave.htm) is reachable on the network
    Affected if Web interface responds and is accessible from your network position
  4. Confirm authentication to web interface is possible
    Attempt to log into the device web interface with valid credentials, or check if authentication mechanisms are enabled
    Affected if You can authenticate to the web interface (or anonymous access is unexpectedly enabled)

If the device is a Sercomm SCE4255W running firmware earlier than DG3934v3@2308041842 AND the web interface is network-accessible with authentication enabled, the environment is affected by this path traversal vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update DG3934v3@2308041842 or later. Until patched, restrict web interface access to trusted authenticated users only and monitor logs for traversal patterns.

Recommended fix Moderate confidence

DG3934v3@2308041842 or later firmware release for Small Cell Sercomm SCE4255W (FreedomFi Englewood)

  1. 1. Identify the current firmware version of the Small Cell Sercomm SCE4255W (FreedomFi Englewood) device via the web interface or administrative console.
  2. 2. Download the fixed firmware version DG3934v3@2308041842 or a later stable release from the official FreedomFi or Sercomm vendor support渠道.
  3. 3. Access the device's web-based administration interface and navigate to the firmware upgrade section (typically under Setup > Firmware or System > Upgrade).
  4. 4. Upload the downloaded firmware image and initiate the upgrade process.
  5. 5. Wait for the device to complete the firmware flash and reboot automatically.
  6. 6. After reboot, verify the new firmware version is DG3934v3@2308041842 or later.
  7. 7. Confirm the vulnerability is resolved by testing that path traversal attempts on /logsave.htm with crafted log_type parameters are now rejected.
Caveat Firmware upgrades on hardware appliances may cause temporary service disruption; ensure backup of configuration and plan for downtime window

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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