Tomofun Furbo 360 up to FB0035_FW_036 Account server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.54 |
Summary
A vulnerability classified as critical has been found in Tomofun Furbo 360 up to FB0035_FW_036. Impacted is an unknown function of the component Account Handler. Performing a manipulation results in server-side request forgery. This vulnerability is reported as CVE-2025-11636. The attack is possible to be carried out remotely. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in Tomofun Furbo 360 up to FB0035_FW_036 (Firmware Software). It has been classified as critical. This affects some unknown processing of the component Account Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability.
The bug was discovered 05/15/2025. The weakness was disclosed by Calvin Star, Julian B (skelet4r and dead1nfluence) with Software Secured. An attacker who compromises the Furbo account of a legitimate user can coerce the device to make a request to an attacker-controlled server by modifying the URL which is sent during the recording of a new treat toss sound. The end result is that the Furbo will download a file from the attacker's server. This vulnerability is uniquely identified as CVE-2025-11636. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a private exploit is available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/31/2025).
It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 149 days. During that time the estimated underground price was around . The vendor was contacted early about this disclosure but did not respond in any way. 1. Create a Frida script hook the treat toss service and replace the URL with an attacker controlled URL 2. Start the Furbo app and Frida Server on a jail broken phone 3. Run the Fride Script 4. In the Furbo app, navigate to the Furbo device settings. 5. Select Treat Toss Sound and enable "Record My Own Sound". 6. Record a short audio clip and Swipe right to push the change. 7. On the attacker-controlled server, observe the inbound request from the Furbo Device.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-33899). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.6
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔒
CNA Base Score: 5.6
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Private
Status: Proof-of-Concept
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/15/2025 Vulnerability found06/21/2025 Vendor informed
07/03/2025 Vendor acknowledged
10/11/2025 Advisory disclosed
10/11/2025 VulDB entry created
10/31/2025 VulDB entry last update
Sources
Researcher: Calvin Star, Julian B (skelet4r, dead1nfluence)Organization: Software Secured
Status: Not defined
CVE: CVE-2025-11636 (🔒)
GCVE (CVE): GCVE-0-2025-11636
GCVE (VulDB): GCVE-100-328047
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/11/2025 20:38Updated: 10/31/2025 04:51
Changes: 10/11/2025 20:38 (51), 10/12/2025 17:57 (29), 10/12/2025 18:45 (1), 10/16/2025 07:41 (16), 10/16/2025 07:44 (5), 10/31/2025 04:51 (12)
Complete: 🔍
Submitter: jTag Labs
Committer: jTag Labs
Cache ID: 216::103
Submit
Accepted
- Submit #661361: Tomofun Furbo 360 ≤ FB0035_FW_036 Server Side Request Forgery (by jTag Labs)
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.