CVE-2026-2824VulnerabilityPublished 20 Feb 2026Updated 23 Feb 2026

CVE-2026-2824: Comfast CF-E7 · Command Injection

Affects Comfast CF-E7Source CVE Database V5

Not known to be exploited · 17% EPSS · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 17.1% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ComfastCF-E7	Affected =2.6.0.9	Fixed in–

AI-suggested

Given the lack of an official patch, organizations should implement the following mitigations: 1) Immediately isolate Comfast CF-E7 devices from untrusted networks by placing them behind firewalls or within segmented network zones to restrict access to the vulnerable web management interface. 2) Disable or restrict access to the /cgi-bin/mbox-config endpoint if possible, or disable the web management interface entirely if not required. 3) Monitor network traffic and device logs for unusual requests targeting the ping_config section or suspicious command execution patterns. 4) Employ intrusion detection/prevention systems (IDS/IPS) with signatures to detect exploitation attempts targeting this vulnerability. 5) Consider replacing affected devices with models from vendors with active security support if mitigation is not feasible. 6) Maintain strict access control policies, ensuring only trusted administrators can reach management interfaces. 7) Regularly audit device firmware versions and configurations to identify and remediate vulnerable instances. 8) Stay alert for vendor updates or community patches addressing this vulnerability.

Description

A flaw has been found in Comfast CF-E7 2.6.0.9. This affects the function sub_441CF4 of the file /cgi-bin/mbox-config?method=SET&section=ping_config of the component webmggnt. Executing a manipulation of the argument destination can lead to command injection. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of this vulnerability is unauthorized remote command execution on affected Comfast CF-E7 devices, which can lead to full compromise of the device. Attackers could manipulate device configurations, intercept or redirect network traffic, or use the device as a foothold for lateral movement within an organization's network. Although the CVSS score is medium, the ease of exploitation without authentication or user interaction increases risk. Compromise of network devices can degrade network availability, compromise confidentiality of internal communications, and undermine integrity of network operations. Organizations relying on these devices for critical network infrastructure or remote connectivity may face operational disruptions and potential data breaches. The absence of vendor patches means that affected devices remain exposed, increasing the window of opportunity for attackers. The exploit's public availability further elevates the threat, as less skilled attackers can leverage existing code to target vulnerable devices.

Summary

CVE-2026-2824 is a command injection vulnerability affecting Comfast CF-E7 wireless devices running firmware version 2.6.0.9. The flaw resides in the web management interface component 'webmggnt', specifically in the CGI script /cgi-bin/mbox-config when invoked with parameters method=SET and section=ping_config. The vulnerability arises from improper sanitization of the 'destination' argument, which an attacker can manipulate to inject arbitrary shell commands. This injection allows remote attackers to execute commands with the privileges of the web management process, potentially leading to unauthorized control over the device. The attack does not require authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, and limited impact on confidentiality, integrity, and availability. The vulnerability affects only firmware version 2.6.0.9, and no other versions are currently reported as vulnerable. The lack of vendor response and patch availability heightens the urgency for users to implement alternative mitigations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 13:40 UTC

Technical details

References

Community reviews

Related threats