CVE-2025-68713: An issue was discovered in Rakuten Send Anywhere (File Transfer) for Android (com.estmob.android.sendanywhe...
An issue was discovered in Rakuten Send Anywhere (File Transfer) for Android (com.estmob.android.sendanywhere) 23.2.9. The vulnerability allows untrusted applications (with no permissions) to force arbitrary file downloads into the app's scoped storage. The resulting files appear in the application's trusted Received interface. These conditions establish a vector for arbitrary code execution if the payload is an APK file, or a denial-of-service condition through resource exhaustion from oversized transfers.
Security readout for executives and security teams
Plain-English summary
Rakuten Send Anywhere for Android 23.2.9 can be made by another untrusted app to download files into its private app storage. Those files then appear in the app’s trusted Received view, creating risk if users open an APK or if oversized transfers exhaust device resources.
Executive priority
Treat as a high-priority mobile app exposure for fleets using Send Anywhere on Android. Prioritize inventory, user warning, and vendor update checks. Business urgency rises where Android sideloading is allowed or devices handle sensitive files.
Technical view
The CVE describes improper Android component exposure or permission enforcement, mapped to CWE-926. A no-permission app can force arbitrary downloads into Send Anywhere scoped storage. The CVSS 3.1 score is 8.0, with confidentiality, integrity, and availability all rated high. Sources do not name a fixed version.
Likely exposure
Exposure is limited to Android devices running Rakuten Send Anywhere package com.estmob.android.sendanywhere version 23.2.9, especially where untrusted apps can be installed or sideloaded. The source bundle does not identify other affected versions.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not show active exploitation. The described attack still requires a local malicious or untrusted app and user interaction for APK execution, while denial of service may come from forced oversized transfers.
Researcher notes
Evidence is based on the CVE record and linked public write-up. The affected CPE data is incomplete, and no fixed version or vendor advisory is provided in the bundle. Avoid assuming broader version impact without vendor confirmation.
Mitigation direction
Inventory Android devices for com.estmob.android.sendanywhere version 23.2.9.
Check Rakuten Send Anywhere vendor guidance for an updated or fixed release.
Remove or disable the affected app where business need is low.
Use MDM controls to restrict untrusted app installation and sideloading.
Warn users not to open unexpected APKs from the Received interface.
Validation and detection
Confirm whether managed devices have the affected package and version installed.
Review mobile telemetry for unexpected files in Send Anywhere received storage.
Check for unusual storage growth on devices using the app.
Verify users cannot install APKs from unknown sources where policy forbids it.
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-926: 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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-926 · source CWE mapping
Improper Export of Android Application Components
Improper Export of Android Application Components represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.