dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-67113

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
OS command injection in the CWMP client (/ftl/bin/cwmp) of Small Cell Sercomm SCE4255W (FreedomFi Englewood) firmware before DG3934v3@2308041842 allows remote attackers controlling the ACS endpoint to execute arbitrary commands as root via a crafted TR-069 Download URL that is passed unescaped into the firmware upgrade pipeline.

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

OS command injection vulnerability in the CWMP (TR-069) client binary (/ftl/bin/cwmp) of Sercomm SCE4255W small cell devices. Attackers with control over the ACS (Auto Configuration Server) endpoint can send a crafted TR-069 Download request with a malicious URL that gets passed unescaped into the firmware upgrade pipeline, enabling arbitrary OS command execution with root privileges.

MitigationApply vendor firmware update DG3934v3@2308041842 or later to all affected devices. If immediate patching is not possible, restrict access to the ACS endpoint and monitor for unauthorized TR-069 traffic to prevent exploitation.

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
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. Identify device model
    Check if the device is a Sercomm SCE4255W small cell by reviewing the device label, web interface, or firmware identification output
    Affected if Device is a Sercomm SCE4255W small cell
  2. Determine firmware version
    Retrieve the installed firmware version from the device web interface, boot logs, or via command line (e.g., cat /etc/version, ver, or firmware info utilities)
    Affected if Firmware version is earlier than DG3934v3@2308041842 (versions without the fix)
  3. Verify CWMP client is enabled
    Check if the CWMP client process (/ftl/bin/cwmp) is running on the device, typically via process list (ps) or service status commands
    Affected if CWMP client (/ftl/bin/cwmp) is actively running and processing TR-069 requests
  4. Inspect ACS configuration
    Examine the ACS (Auto Configuration Server) URL configuration in the CWMP client settings, typically found in the device web interface under TR-069/ACS settings or via configuration file
    Affected if ACS URL points to an untrusted or externally accessible endpoint
  5. Monitor for suspicious TR-069 traffic
    Review network logs or packet captures for TR-069 Download requests with unusual or unexpected URL parameters, especially from the configured ACS endpoint
    Affected if Unusual Download request patterns or unexpected URL values are observed in TR-069 traffic

The device is affected if it is a Sercomm SCE4255W running firmware older than DG3934v3@2308041842 with the CWMP client enabled and configured to connect to an ACS endpoint.

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 to all affected devices. If immediate patching is not possible, restrict access to the ACS endpoint and monitor for unauthorized TR-069 traffic to prevent exploitation.

Recommended fix Moderate confidence

DG3934v3@2308041842 or later

  1. 1. Identify the current firmware version of the Sercomm SCE4255W (FreedomFi Englewood) device
  2. 2. Download the fixed firmware version DG3934v3@2308041842 or later from the official FreedomFi or Sercomm vendor source
  3. 3. Access the device's administrative web interface or use the vendor-provided firmware update mechanism
  4. 4. Upload and apply the firmware update, following vendor instructions carefully
  5. 5. Verify the firmware upgrade completed successfully and the device is operational
  6. 6. After upgrade, confirm the CWMP client (/ftl/bin/cwmp) is no longer vulnerable to command injection via crafted TR-069 Download URLs

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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