/

CVE-2026-29515

Severity:

CRITICAL RISK

(9.8)

Authentication Bypass in MiCode FileExplorer SwiFTP Server

CVE-2026-29515

Analyzed

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-303, CWE-862

Impact:

Unauthorized Access and Data Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MiCode FileExplorer embeds a SwiFTP FTP server component that contains an authentication bypass, allowing any network attacker to log in with arbitrary credentials.

Because the PASS command handler accepts any username/password combination, attackers can gain full FTP access to list, read, write, and delete files exposed by the server.

Affected context

This vulnerability affects deployments of MiCode FileExplorer that have the embedded SwiFTP FTP server enabled or accessible over a network interface.

The issue manifests in the FTP authentication flow, specifically in the handling of the PASS command, where supplied credentials are not actually verified.

Systems are at risk when:

  • The FTP server is reachable over Wi-Fi or other network paths
  • FileExplorer exposes local storage or removable media via FTP
  • Users assume FTP access is protected by username/password authentication

Because the MiCode/Explorer project is end-of-life, the vulnerable behavior is expected to remain in all existing distributions unless locally mitigated.

Exploit preconditions

  • Attack surface: Network-accessible FTP service provided by MiCode FileExplorer.
  • Required access: Network connectivity to the device (e.g., same Wi-Fi network, routed access, or exposed port).
  • Authentication state: No valid credentials are needed; any username and password pair will be accepted by the PASS handler.
  • Trigger point: Sending a standard FTP login sequence (USER + PASS) with arbitrary values.
  • Why exploitation is possible: The PASS command handler does not validate credentials against any real authentication store, effectively disabling authentication and granting a session regardless of input.

Why this happens

The core issue is a flawed authentication implementation where the server-side logic responsible for validating credentials is missing or non-functional.

Specifically, the PASS command handler in the SwiFTP component unconditionally grants access following receipt of a password, without checking:

  • Whether the username exists
  • Whether the password matches any stored secret
  • Whether any authentication state has been correctly established

This maps primarily to CWE-303: Incorrect Implementation of Authentication Algorithm, because the intended security check (credential verification) is either absent or incorrectly implemented.

It is also related to CWE-862: Missing Authorization, as the system fails to enforce access controls after (or independent of) the broken authentication step, allowing any session to perform file operations.

Conceptually, the insecure pattern is treating the completion of an authentication exchange (receiving PASS) as sufficient for access, rather than verifying the supplied secrets and binding them to an access-control decision.

Potential impact

  • Network attackers could log into the FTP server without valid credentials.
  • Attackers may read sensitive files exposed by the FileExplorer FTP share.
  • Attackers could upload or modify files, potentially introducing malicious content or tampering with user data.
  • Files may be deleted or corrupted, leading to data loss.
  • Compromised files could be used as a stepping stone for further attacks if other apps trust or process those files.

General mitigation guidance

Because the upstream project is end-of-life, mitigation typically depends on configuration and environmental controls rather than patches.

Useful defensive patterns include:

  • Disable the FTP server component entirely where possible, or avoid using the FTP sharing feature.
  • Network isolation: Restrict which networks can reach the device's FTP port, such as by limiting to trusted Wi-Fi networks and disabling any port forwarding or remote access.
  • Host-based controls: Use firewall rules, VPN-based access, or tethering configurations that prevent untrusted clients from connecting to the FTP service.
  • Least privilege for exposed data: Share only non-sensitive directories and avoid exposing full device storage; keep sensitive information outside of any FTP-shared paths.
  • Alternative sharing mechanisms: Prefer file-transfer channels that provide robust, well-tested authentication and encryption, such as SFTP through a maintained app or cloud-backed synchronization services.

These approaches reduce reliance on the broken authentication logic and minimize the attack surface even in the absence of vendor fixes.

How teams detect issues like this

Detection and monitoring can focus on identifying both the presence of the vulnerable component and anomalous access patterns.

Common strategies include:

  • Service discovery and inventory: Scan networks for devices exposing FTP services from MiCode FileExplorer or similar FTP banners; maintain an inventory of such endpoints.
  • Configuration review: Manually audit device and application settings to identify where the FTP sharing feature is enabled, especially on shared or corporate networks.
  • Network monitoring: Use intrusion detection systems (IDS) or network monitoring tools to:
  • Flag anonymous or unexpected FTP logins.
  • Correlate FTP sessions with users or devices that should not be using the service.
  • Policy enforcement: Adopt mobile or endpoint management policies that disallow running end-of-life file-sharing apps or unmanaged FTP servers on corporate or sensitive networks.
  • Static analysis / code review (for forks or derivatives): When maintaining forks of MiCode/Explorer or reusing SwiFTP components, review authentication paths to ensure credential validation actually occurs before granting access.

Sources

SourceLink
github.comgithub.com/MiCode/FileExplorer
vulncheck.comvulncheck.com/advisories/micode-fileexplorer-swiftp-server-authentication-bypass

Frequently asked

questions

It can be, but only if the FTP service is exposed beyond the local network, for example via router port forwarding, public Wi-Fi sharing, or VPN routing. In many default setups, exposure is limited to the local network, but any path that allows remote clients to reach the FTP port makes exploitation trivial.

An attacker only needs network-level access to the device's FTP port; no valid credentials are required. Being on the same Wi-Fi network is typically sufficient, and no prior compromise of the device is needed.

The safest pattern is to remove or disable the vulnerable FTP service and replace it with a supported file-sharing mechanism that enforces proven authentication and authorization. Where removal is not immediately feasible, tightly restrict network access and avoid sharing any sensitive directories through the FTP feature.

Future implementations should treat authentication as a first-class, testable component:

  • Implement explicit credential verification and fail-closed behavior for all login paths.
  • Separate authentication from authorization and enforce both consistently.
  • Use standard, vetted authentication libraries or frameworks rather than ad-hoc logic.
  • Add automated tests and security reviews that verify authentication failures when incorrect credentials are supplied.
Find out what's already
exploitable in your codebase.