Loading vulnerability…
On TP-Link Tapo C260 v1, a command injection vulnerability exists due to improper sanitization of certain POST parameters during configuration synchronization. An authenticated attacker can leverage the vulnerable POST parameters to execute arbitrary system commands on the device, potentially resulting in full device compromise.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a Python proof-of-concept exploit chain targeting TP-Link Tapo C260 IP cameras, claiming unauthenticated-to-root RCE by chaining three CVEs (CVE-2026-0651/0652/0653). Structure: (1) exploit.py implements the cloud-based RCE portion: it sends HTTPS POST requests to the TP-Link cloud API endpoint /v1/things/{device_id}/services-sync with mobile-app-like headers and an Authorization token. It first 'poisons' a device configuration value by abusing a passthrough multipleRequest containing method setLedStatus; crafted nested JSON keys write attacker-controlled data into the config path tp_manage/info/dev_name (arbitrary config write). It then 'triggers' execution by sending another passthrough request (testUsrDefAudio -> device_info.set_region_code) which, per comments/README, causes the device to read dev_name and pass it unsanitized into a popen()-backed command path, resulting in command injection and privilege escalation to root. Payload options include a netcat-based reverse shell (mkfifo + /bin/sh -i | nc), a curl callback, or an arbitrary command string. The script optionally restores dev_name after exploitation. (2) lfd.py is a separate local-network helper for CVE-2026-0651: it performs an HTTPS GET to https://{host}/stok={token}/%2e%2e%2f... to traverse out of /www and read arbitrary files (e.g., /etc/passwd), requiring a valid stok token. requirements.txt pins requests/urllib3. Overall purpose: demonstrate and automate the exploit chain (config poisoning + trigger) and provide a standalone file disclosure tool; TLS certificate verification is disabled in both scripts.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.