FileWrangler <= 5.30 suffers from a stack-based buffer overflow vulnerability when parsing directory listings from an FTP server. A malicious server can send an overlong folder name in response to a LIST command, triggering memory corruption during client-side rendering. Exploitation requires passive user interaction—simply connecting to the server—without further input. Successful exploitation may lead to arbitrary code execution.
Security readout for executives and security teams
Plain-English summary
FileWrangler versions up to 5.30 can be compromised when a user connects to a malicious FTP server. The server can return an overly long folder name that corrupts memory in the client. Successful exploitation may allow arbitrary code execution. The bundle does not show active KEV-listed exploitation.
Executive priority
Treat this as a high-priority legacy software risk, especially in environments that still permit FTP client use. The business concern is endpoint compromise through normal-looking user activity, not server exposure. Prioritize inventory, removal, and outbound FTP restrictions.
Technical view
This is a stack-based buffer overflow in FileWrangler directory-listing parsing. A malicious FTP server response to LIST can trigger memory corruption during client-side rendering. The source bundle identifies CWE-121 and CVSS 4.0 score 8.5 with passive user interaction required and no privileges required.
Likely exposure
Exposure is likely limited to environments where CursorArts FileWrangler, especially version 5.30 or earlier, remains installed and used for FTP connections. Risk increases when users connect to unknown, external, or attacker-controlled FTP servers.
Exploitation context
Public exploit references are listed in the bundle, including Corelan, Rapid7 Metasploit, and Exploit-DB. KEV is false, so active exploitation is not established by the supplied evidence. Exploitation requires the client to connect to a malicious FTP server.
Researcher notes
The affected-version data is inconsistent: the title and description say FileWrangler <= 5.30, while the affected object lists version 0 with unknown default status. Use the CVE record and third-party advisory for scoping, but validate locally before declaring exposure.
Mitigation direction
Inventory endpoints for FileWrangler installations and version information.
Remove or replace FileWrangler where it is no longer required.
Check CursorArts or trusted vendor guidance for any fixed release or advisory.
Restrict FileWrangler use to known, trusted FTP servers only.
Block unnecessary outbound FTP access from managed endpoints.
Validation and detection
Search software inventory for CursorArts FileWrangler and affected versions.
Review endpoint telemetry for recent FileWrangler process execution.
Review network logs for outbound FTP connections from FileWrangler hosts.
Confirm whether users can connect to arbitrary FTP servers.
Document compensating controls where removal is not immediately possible.
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 · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.