CVE Intelligence

Tomofun vulnerabilities

🔔 Create alert RSS

Published CVEs affecting Tomofun products: 4 record(s), with severity, exploitation and fixes.

Exploited only (KEV) →

CVE-2025-11645 Low · 2.4 CWE-200 Oct 12, 2025
Tomofun Furbo Mobile App Authentication Token sensitive information
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.
CVE-2025-11637 Low · 3.7 CWE-362 Oct 12, 2025
Tomofun Furbo 360 Audio race condition
A vulnerability was detected in Tomofun Furbo 360 up to FB0035_FW_036. Impacted is an unknown function of the component Audio Handler. Performing manipulation results in race condition. The attack is possible to be carried out remotely. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2025-11636 High · 8.1 CWE-918 Oct 12, 2025
Tomofun Furbo 360 Account server-side request forgery
A security vulnerability has been detected in Tomofun Furbo 360 up to FB0035_FW_036. This issue affects some unknown processing of the component Account Handler. Such manipulation leads to server-side request forgery. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2025-11635 Medium · 6.5 CWE-400 Oct 12, 2025
Tomofun Furbo 360 File Upload resource consumption
A weakness has been identified in Tomofun Furbo 360 up to FB0035_FW_036. This vulnerability affects unknown code of the component File Upload. This manipulation causes resource consumption. Remote exploitation of the attack is possible. The vendor was contacted early about this disclosure but did not respond in any way.