CVE-2025-11649
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 · uneditedA vulnerability was found in Tomofun Furbo 360 and Furbo Mini. The affected element is an unknown function of the component Root Account Handler. Performing manipulation results in use of hard-coded password. The attack must be initiated from a local position. The attack is considered to have high complexity. The exploitability is described as difficult. The exploit has been made public and could be used. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceHard-coded password vulnerability in the Root Account Handler component of Tomofun Furbo 360 and Furbo Mini pet camera firmware. The vulnerability allows a local attacker with high-complexity access to potentially obtain root credentials. Affected versions are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074.
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<= 074<= 036CVSS 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
- Physical
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Furbo device modelLocate the model number on the device physical label or in the mobile app device settings. Confirm whether the unit is a Furbo 360 or Furbo Mini.Affected if Device is neither Furbo 360 nor Furbo Mini - this CVE does not apply.
-
Determine installed firmware versionAccess the Furbo mobile app, go to device settings, and look for firmware version information. Alternatively, check the device web interface or API if accessible.Affected if Unable to determine firmware version - cannot confirm vulnerability status.
-
Compare firmware version to affected rangesFor Furbo 360: check if version is FB0035_FW_036 or lower. For Furbo Mini: check if version is MC0020_FW_074 or lower.Affected if Furbo 360 with FB0035_FW_036 or lower, OR Furbo Mini with MC0020_FW_074 or lower - device is potentially affected.
-
Assess local access exposureEvaluate physical security and network accessibility of the device. Determine if unauthorized local attackers could plausibly gain high-complexity access to the device.Affected if Device is in an accessible location with weak physical or network controls - exploitability increases significantly.
You are affected if you have a Furbo 360 device running firmware FB0035_FW_036 or lower, or a Furbo Mini device running firmware MC0020_FW_074 or lower, and the device could be accessed by a local attacker with high-complexity access.
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 dataSince the vendor did not respond to the disclosure, organizations should isolate these devices on restricted network segments, monitor for unauthorized local access, and consider replacing affected units if no firmware update becomes available.
- Consultation6.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 $4,368.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11649 — 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-11649 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