The Belkin WeMo Home Automation firmware before 3949 does not properly use the STUN and…
Priority MEDIUM 44CWE-264Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- — Not recorded in CVSS 2.0
- Attack complexity
- Medium
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Complete · Complete · Complete
- Fix status
- No fix listed
Attack profile from CVSS 2.0 · NVD. Fix status from CNA. Impact type from CWE-264.
Summary
The Belkin WeMo Home Automation firmware before 3949 does not properly use the STUN and TURN protocols, which allows remote attackers to hijack connections and possibly have unspecified other impact by leveraging access to a single WeMo device.
Why it matters now
EPSS 0.01866 79th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2013-6949
- 2026-10-03 Alias added: GHSA-m5gm-p83p-6vg3
References
More Belkin Wemo Home Automation Firmware vulnerabilities
- TI-2013-05713 The Belkin WeMo Home Automation firmware before 3949 has a hardcoded GPG key, which makes… CVSS 2.0HIGH 10.0
- TI-2013-05709 The peerAddresses API in the Belkin WeMo Home Automation firmware before 3949 allows… CVSS 2.0HIGH 7.8
- TI-2013-05711 The Belkin WeMo Home Automation firmware before 3949 does not use SSL for the… CVSS 2.0HIGH 7.8
- TI-2013-05712 The Belkin WeMo Home Automation firmware before 3949 does not maintain a set of… CVSS 2.0HIGH 7.1
Sources
- CVE-2013-6949 · CVE Program
- CVE-2013-6949 · NVD
- FIRST EPSS
- GHSA-m5gm-p83p-6vg3 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences