dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6799

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 security flaw has been discovered in Comfast CF-N1-S 2.6.0.1. Affected by this issue is some unknown functionality of the file /cgi-bin/mbox-config?method=SET&section=ping_config of the component Endpoint. Performing a manipulation of the argument destination results in command injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

Command injection vulnerability in Comfast CF-N1-S 2.6.0.1 web interface (cgi-bin/mbox-config) allows remote attackers to execute arbitrary OS commands via the destination parameter in the ping_config function. The issue stems from insufficient input sanitization before passing user-supplied data to system calls.

MitigationSince the vendor did not respond and no patch is available, implement network segmentation to isolate the device, deploy WAF/IPS rules to detect and block command injection patterns in HTTP requests to /cgi-bin/mbox-config, or replace the device with a supported alternative.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 device model
    Access the device web interface or check the device label/documentation to confirm the model is Comfast CF-N1-S
    Affected if The device is not a Comfast CF-N1-S unit
  2. Check firmware version
    Log into the web interface and navigate to the system status or firmware upgrade page to view the installed firmware version, or use the device's CLI if available
    Affected if The firmware version is 2.6.0.1
  3. Confirm web interface is accessible
    Attempt to access the device web interface via HTTP/HTTPS on the default management port (typically 80 or 443)
    Affected if The web interface is exposed and reachable on the network
  4. Verify vulnerable endpoint exists
    Send an HTTP request to /cgi-bin/mbox-config on the device to confirm the CGI script is present and responds
    Affected if The /cgi-bin/mbox-config endpoint returns a valid HTTP response (200 or other) rather than a 404 error

The device is affected if it is a Comfast CF-N1-S running firmware version 2.6.0.1 with an accessible web interface that exposes the /cgi-bin/mbox-config endpoint containing the ping_config function.

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

Since the vendor did not respond and no patch is available, implement network segmentation to isolate the device, deploy WAF/IPS rules to detect and block command injection patterns in HTTP requests to /cgi-bin/mbox-config, or replace the device with a supported alternative.

Recommended fix Moderate confidence
  1. 1. Isolate the affected Comfast CF-N1-S router from untrusted networks using network segmentation or VLANs
  2. 2. If remote management is not required, disable the web interface/cgi-bin endpoints from external access via firewall rules
  3. 3. If the ping functionality is not business-critical, disable or restrict it at the network perimeter
  4. 4. Monitor network traffic for suspicious requests to /cgi-bin/mbox-config endpoints
  5. 5. Consider replacing the device with a model that receives security updates from the vendor
  6. 6. If possible, implement intrusion detection/prevention rules to detect command injection attempts in HTTP parameters
Caveat No vendor patch or fixed version is available. The vendor (Comfast) did not respond to the security disclosure.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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