Skip to main content
VulnerabilityPublished

CVE-2025-60787: motionEye vulnerable to RCE via unsanitized motion config parameter

Affects motioneyeSource GCVE Database

0
Compare
Authoritative record:CVE-2025-60787· High 7.2

Public exploit available (Metasploit, Exploit-DB) · CVSS 7.2 High : upgrade to 0.43.1b5 as a priority.

Data as of 30 Oct 2026, 02:08 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.43.1b5
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 3 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 7 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , the same day as disclosure

  4. , 131 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade motioneye to 0.43.1b5.

Affected software

ProductAffectedFixed in
PyPImotioneyeAffected
  • <0.43.1b5
Fixed in
  • 0.43.1b5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading MotionEye to version 0.43.1b5 or later. This update sanitizes user input in configuration fields to prevent command injection. Until patched, administrators should restrict access to the Web UI to trusted users only and consider running the container with minimal privileges. Note that client-side validation can be bypassed and is not a reliable mitigation.

Description

MotionEye versions prior to 0.43.1b5 contain a command injection vulnerability in the handling of certain configuration parameters via the Web UI. Unsanitized user input in fields like image_file_name and movie_filename is written directly into Motion configuration files and interpreted by the shell when the Motion service restarts. This allows authenticated attackers with high privileges to execute arbitrary commands inside the MotionEye container, potentially leading to full container and host compromise depending on container privileges. Client-side validation attempts to block malicious input but can be bypassed via browser console manipulation. A fix is available in version 0.43.1b5.

References

Community reviews

Loading reviews…