CVE-2025-60787
MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as image_file_name.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 18.5%, higher than 97% of all known CVEs. Patch or mitigate before the next change window.
Description
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.
- CVSS 3.1
- 7.2 HIGHCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 18.46% probability · 97th percentile
- Public exploits
- 1 in Exploit-DB · first 11 February 2026
- CISA KEV
- Not listed
- Weakness
- CWE-20, CWE-78, CWE-116
- Affected
- motioneye project/motioneye
- Source
- cve@mitre.org
EPSS 18.5% since 1 November 2026; no change recorded yet. The dashed line is the ten per cent mark our analysts treat as “patch before the next change window”. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
Public exploits (1)
Entries in Exploit-DB that cite this CVE. Links go to the Exploit-DB page and to the file in the public repository; nothing is hosted here. A verified tick means the Exploit-DB team confirmed the exploit works against the stated version.
References
- https://github.com/prabhatverma47/motionEye-RCE-through-config-parameterExploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.