dbcve.org
FileexplorerApplication · Xiaomi

CVE-2026-29515

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MiCode FileExplorer contains an authentication bypass vulnerability in the embedded SwiFTP FTP server component that allows network attackers to log in without valid credentials. Attackers can send arbitrary username and password combinations to the PASS command handler, which unconditionally grants access and allows listing, reading, writing, and deleting files exposed by the FTP server. The MiCode/Explorer open source project has reached end-of-life status.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MiCode FileExplorer's embedded SwiFTP FTP server contains an authentication bypass where the PASS command handler unconditionally grants access regardless of credentials supplied. Network attackers can send arbitrary username/password combinations to gain full file system access including listing, reading, writing, and deleting files exposed by the FTP server.

MitigationSince MiCode/Explorer is end-of-life and unlikely to receive patches, organizations should either disable the FTP server component if unused, implement network segmentation/firewall rules to prevent external access to the FTP service, or migrate to an actively maintained alternative file management solution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FileexplorerApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if MiCode FileExplorer is installed
    On Android, go to Settings > Apps and look for 'FileExplorer' or 'Mi Explorer' by Xiaomi, or run: pm list packages | grep -i 'xiaomi\|fileexplorer\|miexplorer'
    Affected if The app is present on the device
  2. Verify FTP service is running
    Check if port 2121 (default SwiFTP port) or port 21 is listening: netstat -tuln | grep -E ':(21|2121)' or ss -tuln | grep -E ':(21|2121)'
    Affected if Port 2121 or 21 is listening, indicating FTP server is active
  3. Confirm FTP service accepts any authentication
    Connect to the FTP server using any IP on the network and test with a fabricated username and random password: ftp <device_ip>:2121, then enter any username like 'test' and any password like 'wrongpass' when prompted
    Affected if Login succeeds with arbitrary credentials, confirming the authentication bypass
  4. Check network exposure of FTP service
    If FTP is listening, verify who can reach it: check firewall rules (iptables -L) or router port forwarding settings for ports 21/2121
    Affected if FTP port is exposed to untrusted networks or the internet

You are affected if MiCode FileExplorer is installed and its built-in SwiFTP server is enabled and accessible, since it accepts any username/password combination granting full file system access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since MiCode/Explorer is end-of-life and unlikely to receive patches, organizations should either disable the FTP server component if unused, implement network segmentation/firewall rules to prevent external access to the FTP service, or migrate to an actively maintained alternative file management solution.

Recommended fix High confidence
  1. 1. Identify all systems running MiCode FileExplorer with the embedded SwiFTP FTP server component
  2. 2. Disable or uninstall the SwiFTP FTP server component if not required for business operations
  3. 3. If the FTP server is required, implement network-level access controls: configure firewall rules to restrict FTP access to only trusted IP addresses or VPN networks
  4. 4. Consider migrating to an actively maintained file transfer solution that receives security updates
  5. 5. Monitor network logs for any unauthorized FTP access attempts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fileexplorer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29515 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29515 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data