Furbo 360 CVE-2025-11636
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach network-exposed Account Handler endpoint
-
ExploitCraft request with attacker-controlled URL/parameter
-
ExecutionTrigger server-side request forgery
-
ImpactCoerce backend to contact internal/metadata services
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation targets the Furbo 360 Dog Camera's Account Handler component and requires crafting input that the server consumes to initiate an outbound request, redirecting it to an attacker-specified destination (SSRF). The primary limiting factor is the HIGH attack complexity (AC:H) - VulDB explicitly rates exploitability as 'difficult,' indicating success depends on non-trivial conditions (specific request formatting, timing, or bypass of input filtering) rather than a straightforward request. The supplied vector states no authentication is required (PR:N) and no user interaction (UI:N), but because the vulnerable component is the 'Account Handler,' defenders should verify whether a valid account or session is in fact needed, as this would materially raise the exploitation bar. Impact is inherently limited (low confidentiality/integrity/availability), so even successful SSRF likely yields constrained internal access rather than full device or backend takeover. |
| Impact | This is a genuinely moderate-risk issue that does not warrant emergency prioritization. The CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:N/UI:N) describes a network-reachable flaw with HIGH attack complexity, and the vendor (via VulDB/VulDB's CNA cna@vuldb.com) explicitly rates exploitability as 'difficult' - a signal that strongly tempers the network attack vector. Impact is limited across the board (VC:L/VI:L/VA:L), consistent with SSRF (CWE-918) that typically yields limited internal reconnaissance or limited data exposure rather than full compromise. Corroborating signals point the same direction: EPSS is 0.40% (33rd percentile), there is NO CISA KEV listing, and no public exploit code is referenced - so there is no public exploit identified at time of analysis and no confirmed active exploitation. All signals are internally consistent (low EPSS + high AC + low impact + no KEV/POC), which raises confidence that this is a real-but-low-urgency finding rather than a high-CVSS/low-real-risk mismatch. One point to verify with the vendor: the affected component is the 'Account Handler,' which may imply an account/authentication context, yet the CVSS vector asserts PR:N (unauthenticated) - authentication requirements should be confirmed independently since the description alone does not resolve this. |
| Exploit ScenarioDerived | A remote attacker crafts a malicious request to the Furbo 360 camera's cloud/device Account Handler, abusing a parameter that the server uses to make outbound requests, coercing the server into contacting an attacker-chosen internal or external endpoint (SSRF). Because the flaw carries high attack complexity and is rated 'difficult' to exploit, success likely depends on specific timing, encoding, or environmental conditions rather than a trivial single request. No public proof-of-concept exploit is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Server-side request forgery in Tomofun's Furbo 360 dog camera firmware (builds up to FB0035_FW_036) lets remote, unauthenticated attackers manipulate the Account Handler component into issuing outbound requests to destinations of their choosing, potentially reaching internal network services or cloud metadata endpoints. The supplied CVSS vector carries PR:N and UI:N, so no credentials or user interaction are indicated, but both the provided CVSS 4.0 vector and our assessment rate attack complexity as High (AC:H) and VulDB describes exploitability as 'difficult,' meaning success hinges on non-trivial request crafting, timing, or filter bypass rather than a simple request. Impact is constrained (low confidentiality, integrity and availability); EPSS is only 0.40% (33rd percentile), no public exploit identified at time of analysis, and the vendor was contacted early but did not respond.
RemediationAI
No vendor-released patch identified at time of analysis, and because Tomofun did not respond to the coordinated disclosure no fixed firmware version can be cited. Until a vendor fix appears, isolate the Furbo 360 on a dedicated IoT or guest VLAN that is firewalled away from internal networks, and apply egress filtering that denies camera-originated traffic to RFC1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback (127.0.0.0/8), link-local (169.254.0.0/16) and cloud metadata addresses such as 169.254.169.254; the trade-off is that overly broad egress rules can break legitimate cloud connectivity, remote viewing and notifications, so allow only the specific vendor endpoints the camera genuinely needs. If the account registration/linking workflow is not required, avoid using it in the companion app, and monitor the camera's outbound connections for unexpected destinations or internal IP targets, which would indicate SSRF activity. Periodically recheck the VulDB entry at https://vuldb.com/?id.328047 and the vendor's support site for firmware updates; given EPSS of only 0.40% and no public exploit identified at time of analysis, this is a moderate-risk item suitable for scheduled hardening rather than emergency patching.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-918 (server-side request forgery) in the Account Handler component of the Furbo 360 camera firmware. In this class of flaw, the application accepts an attacker-influenced value - a URL, hostname, or callback address used during account registration, linking, or similar account workflows - and performs an outbound HTTP/S request to that value without validating or restricting the destination, so the request originates from the device or its backend handler and can bypass perimeter controls to reach internal-only services, link-local or metadata endpoints, or other hosts on the camera's home network. The CPE string cpe:2.3:o:furbo:furbo_360_dog_camera_firmware:*:*:*:*:*:*:*:* identifies the affected platform as Furbo 360 camera firmware with a wildcard version, so the CPE does not pin an exact build; the description bounds the issue at FB0035_FW_036 and earlier. High attack complexity (AC:H in both the supplied CVSS 4.0 vector and the assessed CVSS 3.1 vector) reflects that exploitation depends on specific request formatting, timing, or bypass of input filtering rather than a single straightforward request, and the Account Handler naming suggests defenders should verify whether a valid account or session is actually required even though the vector states PR:N.
Know when Furbo 360 Dog Camera Firmware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Network-reachable SSRF but vendor-rated 'difficult' justifies AC:H; PR:N retained per supplied vector though the Account Handler context leaves authentication unconfirmed; impact limited, so C/I/A all Low.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Affected Products (CPE)CVE.org
Server-side request forgery in Tomofun Furbo 360 and Furbo Mini dog cameras allows remote attackers to manipulate the TF
A hard-coded root password in the Tomofun Furbo 360 and Furbo Mini pet cameras allows local attackers with low privilege
Improper access controls in the GATT Service of Tomofun Furbo 360 and Furbo Mini dog cameras allow local network attacke
Resource exhaustion in the Tomofun Furbo 360 dog camera (firmware through FB0035_FW_036) lets a remote attacker with val
A race condition in the audio handler of Tomofun's Furbo 360 dog camera firmware (through FB0035_FW_036) allows a remote
Information disclosure vulnerability in Tomofun Furbo 360 and Furbo Mini dog cameras allows local network attackers to e
Insecure storage of sensitive information in Tomofun Furbo 360 and Furbo Mini dog cameras via UART interface allows phys
Weak cryptographic hash implementation in Tomofun Furbo 360 and Furbo Mini firmware allows local attackers with low priv
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB