CVE-2026-28373
Path Traversal in Stackfield Desktop App Allows Arbitrary File Write
Publication date: 2026-04-03
Last updated on: 2026-04-03
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| stackfield | desktop_app | to 1.10.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Stackfield Desktop App versions before 1.10.2 for macOS and Windows have a path traversal vulnerability in their decryption functionality. This vulnerability occurs when processing the filePath property, allowing a malicious export to write arbitrary content to any location on the victim's filesystem.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to write arbitrary files anywhere on the victim's filesystem. This could lead to unauthorized modification or creation of files, potentially enabling further attacks such as code execution, data corruption, or system compromise.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided context and resources do not explicitly discuss the impact of CVE-2026-28373 on compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from a path traversal flaw in the Stackfield Desktop App's decryption of encrypted exports, specifically involving crafted filePath and fileGuid values that allow writing files outside the intended directory.
Detection involves monitoring for suspicious file writes to sensitive locations such as the Windows Startup folder (e.g., AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup) or macOS environment files (e.g., ~/.zshenv, ~/.ssh/authorized_keys) that could indicate exploitation attempts.
Since the vulnerability is triggered when decrypting malicious exports, one detection approach is to audit or monitor the Stackfield Desktop App's decryption activity and file writes during import of organizational data exports.
No specific commands are provided in the resources, but general suggestions include:
- On Windows, use PowerShell or command prompt to check for unexpected files in the Startup folder: `Get-ChildItem "$env:APPDATA\Microsoft\Windows\Start Menu\Programs\Startup"`
- On macOS, check for suspicious modifications or new files in ~/.zshenv or ~/.ssh/authorized_keys using commands like `ls -la ~/.zshenv ~/.ssh/authorized_keys` or `stat ~/.zshenv ~/.ssh/authorized_keys`.
- Monitor file system changes during or after Stackfield Desktop App usage, especially when importing encrypted exports.
Because exploitation requires user interaction (importing a malicious export), monitoring user activity related to import operations may also help detect attempts.
What immediate steps should I take to mitigate this vulnerability?
The primary and immediate mitigation step is to update the Stackfield Desktop App to version 1.10.2 or later, as this version contains the fix for the path traversal vulnerability.
Avoid importing encrypted exports from untrusted or unknown sources, as the vulnerability is triggered during the decryption of such exports.
Ensure that users are aware of the risk and do not open or import suspicious organizational data exports.
If updating immediately is not possible, consider restricting write permissions to sensitive directories such as the Windows Startup folder or macOS environment files to limit the impact of potential exploitation.
Monitor for suspicious file creation or modification in critical system locations as a temporary detection measure.