CVE-2025-11641
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 determined in Tomofun Furbo 360 and Furbo Mini. This impacts an unknown function of the component Trial Restriction Handler. This manipulation causes improper access controls. It is feasible to perform the attack on the physical device. The attack is considered to have high complexity. The exploitability is said to be difficult. 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 confidenceThe Tomofun Furbo 360 and Furbo Mini pet cameras contain an improper access control vulnerability in the Trial Restriction Handler component. This allows bypassing trial period restrictions, likely enabling unauthorized access to premium features without proper authorization. The attack requires physical access to the device, has high complexity, and affects firmware versions up to FB0035_FW_036 (Furbo 360) and MC0020_FW_074 (Furbo Mini).
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Furbo device modelLocate the model number on the device label or check the companion mobile app device settings to confirm whether you have a Furbo 360 or Furbo MiniAffected if The device is a Furbo 360 or Furbo Mini pet camera
-
Check the installed firmware versionAccess the device settings via the Furbo mobile app or web interface and navigate to the firmware or software version information sectionAffected if The firmware version is FB0035_FW_036 or lower for Furbo 360, or MC0020_FW_074 or lower for Furbo Mini
-
Verify if trial period features are activeCheck the device or mobile app for any active trial period, premium trial, or limited-time feature indicatorsAffected if A trial period or limited-time premium features are currently enabled on the device
-
Confirm physical access exposureAssess whether the device could be accessed by unauthorized individuals who could interact with it physicallyAffected if The device is in an area accessible to persons who should not have physical access to it
-
Review trial restriction handler configurationIf accessible via admin interface, check for any configuration settings related to trial restrictions, premium feature locks, or time-based access controlsAffected if A Trial Restriction Handler or similar component with configurable restrictions exists and is enabled
You are affected if you have a Furbo 360 with firmware FB0035_FW_036 or lower, or a Furbo Mini with firmware MC0020_FW_074 or lower, and the device has trial-based feature restrictions that could be bypassed with physical 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 disclosure, apply physical security controls to prevent unauthorized device access, segment the device network, and contact Tomofun directly to request a firmware patch addressing the access control flaw in the trial restriction logic.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11641 — 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-11641 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