CVE-2025-27387
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 · uneditedOPPO Clone Phone uses a weak password WiFi hotspot to transfer files, resulting in Information disclosure.
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 · low confidenceOPPO Clone Phone's WiFi hotspot file transfer feature uses weak passwords for the ad-hoc WiFi network, allowing nearby attackers to potentially join the network and intercept transferred files containing sensitive user data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm OPPO Clone Phone is installedCheck your device's app list or settings > apps for an app named 'Clone Phone', 'OPPO Clone Phone', or similar OPPO file transfer utilityAffected if The app is present on the device
-
Identify the installed app versionGo to device Settings > Apps > Clone Phone (or OPPO Clone Phone) > App info, then record the version number displayedAffected if Version cannot be determined or falls within any affected range provided by OPPO security advisories
-
Determine if WiFi hotspot transfer has been usedOpen the Clone Phone app and navigate to its transfer or hotspot settings; look for WiFi hotspot, 'WiFi direct transfer', or ad-hoc network transfer featuresAffected if The WiFi hotspot file transfer feature has been enabled or recently used
-
Check for active ad-hoc WiFi connectionsCheck your device's WiFi settings for any connected ad-hoc or peer-to-peer networks named with OPPO or Clone Phone identifiers, or look for unexpected WiFi activityAffected if An active or recent ad-hoc WiFi connection from this feature is detected
-
Review transferred files for sensitivityExamine your file transfer history within the Clone Phone app or device logs to identify any sensitive files (personal photos, documents, credentials) transferred via this featureAffected if Sensitive user data has been transferred through the WiFi hotspot feature
If you have OPPO Clone Phone installed with the WiFi hotspot file transfer feature enabled or recently used, your sensitive files may have been vulnerable to interception by nearby attackers due to weak network passwords.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUsers should avoid transferring sensitive files over this feature until OPPO releases a patch implementing stronger authentication or encryption; alternatively, use alternative secure transfer methods.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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