Security readout for executives and security teams
Plain-English summary
FNT Command 13.4.0 has a high-severity flaw that can let an authenticated network user execute code through the C Base Module. Successful exploitation could compromise confidentiality, integrity, and availability of the system.
Executive priority
Treat as a near-term remediation item for any exposed FNT Command 13.4.0 deployment because impact is full system compromise, though active exploitation is not evidenced here.
Technical view
The CVE describes code execution in FNT Command 13.4.0 via the C Base Module. It is mapped to CWE-434 and scored CVSS 8.8 with network attack vector, low complexity, low privileges required, no user interaction, and high impact across CIA.
Likely exposure
Organizations running FNT Command 13.4.0, especially where low-privileged users can reach the C Base Module over the network, are the likely exposure group. The CVE metadata does not provide CPEs or broader affected-version ranges.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. A public Gist is referenced, but the provided bundle does not establish exploit use in the wild.
Researcher notes
The record is sparse: affected vendor/product fields are listed as n/a, while the description names FNT Command 13.4.0. Avoid assuming other versions are affected without vendor confirmation.
Mitigation direction
Check FNT vendor guidance for fixed versions or official workarounds.
Restrict network access to FNT Command administrative and module interfaces.
Limit C Base Module access to necessary trusted users only.
Review upload and file-handling controls associated with the module.
Monitor affected systems for unexpected code execution or file activity.
Validation and detection
Confirm whether FNT Command 13.4.0 is deployed in the environment.
Identify which users can access the C Base Module.
Determine whether the module is reachable from untrusted networks.
Review logs for suspicious uploads, module activity, or process execution.
Track vendor advisories for authoritative remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.