This page lists publicly disclosed CVE vulnerabilities affecting motioneye_project motioneye (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-60787 | MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as image_file_name. Unsanitized user input is written to Motion configuration files, allowing remote authenticated attackers with admin access to achieve code execution when Motion is restarted. | [email protected] | 7.2 | 57.92% | 2025-10-03 | 2025-10-10 |
| CVE-2022-25568 | MotionEye v0.42.1 and below allows attackers to access sensitive information via a GET request to /config/list. To exploit this vulnerability, a regular user password must be unconfigured. | [email protected] | 7.5 | 85.31% | 2022-03-24 | 2024-11-21 |
| CVE-2021-44255 | Authenticated remote code execution in MotionEye <= 0.42.1 and MotioneEyeOS <= 20200606 allows a remote attacker to upload a configuration backup file containing a malicious python pickle file which will execute arbitrary code on the server. | [email protected] | 7.2 | 13.64% | 2022-01-31 | 2024-11-21 |