Magicsmotion's vulnerability footprint centers on the Flamingo 2 device and its firmware, with the observed weaknesses concentrated in sensitive-data handling—specifically cleartext storage and transmission of credentials and other sensitive information. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Magicsmotion over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-12731HIGH The MagicMotion Flamingo 2 application for Android stores data on an sdcard under com.vt.magicmotion/files/Pictures, whence it can be read by other applications. | Jul 15, 2021 | 7.5 | 19 | NO | NO |
CVE-2020-12730MEDIUM MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery. | Jul 15, 2021 | 5.3 | 16 | NO | NO |
CVE-2020-12729MEDIUM MagicMotion Flamingo 2 has a lack of access control for reading from device descriptors. | Jul 15, 2021 | 4.6 | 14 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Magicsmotion.
Media articles that mention a CVE ID that affects a product developed by Magicsmotion — matched by CVE ID, not by vendor name.