VulnerabilityPublished 12 Oct 2025Updated 18 Oct 2025

CVE-2025-11645: Tomofun Furbo Mobile App · Insecure Storage of Sensitive Information

Affects Tomofun Furbo Mobile AppSource CVE Database V5

Public exploit available · CVSS 2.4 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

2.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Physical
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Tomofun Furbo Mobile App	Affected =7.57.0	Fixed in–

AI-suggested

Enforce strict physical security controls to prevent unauthorized access to devices running the Furbo app, including employee and customer devices.
Ensure full device encryption is enabled on all Android devices to protect stored data at rest.
Encourage users to set strong device lock mechanisms (PIN, password, biometric) to reduce risk of token extraction.
Monitor for suspicious activity on Furbo accounts that could indicate token misuse or unauthorized access.
If possible, revoke and regenerate authentication tokens periodically or after device loss/theft.
Consider isolating Furbo app usage to dedicated devices with limited access to sensitive corporate data.
Advocate for vendor engagement and demand a patch or secure token storage improvements.
Educate users about risks of physical device compromise and secure handling of their devices.
Employ mobile device management (MDM) solutions to enforce security policies and remotely wipe devices if compromised.
Review server-side token validation mechanisms to ensure tokens cannot be easily reused or exploited if stolen.

Description

A security vulnerability has been detected in Tomofun Furbo Mobile App up to 7.57.0a on Android. This affects an unknown part of the component Authentication Token Handler. The manipulation leads to insecure storage of sensitive information. It is possible to launch the attack on the physical device. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact is primarily on user privacy and potential unauthorized access to Furbo accounts. Organizations using Furbo devices for pet monitoring or customer engagement may face reputational damage if user data is compromised. The vulnerability could allow attackers to hijack user sessions or access live video feeds if tokens are reused or poorly protected server-side, potentially violating GDPR requirements on personal data protection. However, the low CVSS score and requirement for physical access limit large-scale remote exploitation risks. The main concern is insider threats or theft of devices from employees or customers. This could lead to unauthorized surveillance or data leakage. Organizations should consider the risk in contexts where Furbo devices are deployed in sensitive environments or where user trust is critical. The lack of vendor response and patch increases the window of exposure, necessitating proactive mitigation. Overall, the threat is moderate but should not be ignored given the sensitivity of authentication tokens and potential privacy implications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Oct 2025, 21:00 UTC

Technical details

References

Community reviews

Related threats