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.
Severity
CVSS 3.1
7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
19%(unchanged from 19% a week ago; 18% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-10-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20Improper Input Validation CWE-78Improper Neutralization of Special Elements used in an OS Command (OS Command Injection) CWE-116Improper Encoding or Escaping of Output
Show the promptExplain CVE-2025-60787 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-60787?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-60787?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-60787 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
gunzf0x/CVE-2025-60787Harbor Check: matches CVE10 stars, Python, created PoC for CVE-2025-60787 - Authenticated RCE in motionEye for all versions up to 0.43.1b4 (included)
Rohitberiwala/CVE-2025-60787-MotionEye-RCEHarbor Check: matches CVE1 star, Python, created Professional PoC for CVE-2025-60787: Remote Code Execution in MotionEye (<= 0.43.1b4). This exploit demonstrates an OS Command Injection vu…
diamorphine666/CVE-2025-60787Harbor Check: matches CVE0 stars, Python, created MotionEye OS Command Injection (CVE-2025-60787)
agent-skywalker/CVE-2025-60787Harbor Check: matches CVE0 stars, Python, created MotionEye v0.43.1b4 OS Command Injection
d3vn0mi/CVE-2025-60787-POCHarbor Check: matches CVE0 stars, Python, created Python PoC for CVE-2025-60787, authenticated OS command injection RCE in motionEye <= 0.43.1b4 via unsanitized image_file_name config