CVE-2025-60787

Exp

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.

Published: 2025-10-03 Last update: 2025-10-10 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-60787 is rated High Exploit Risk (73.2/100): CVSS High severity, with high exploitation likelihood (EPSS 57.92%, 98th percentile). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-60787

EDB-ID Source Kind Published Link
52481 exploit_db edb 2026-02-11 Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-60787

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 65.29% 57.92% -7.37%
2 2026-05-07 61.55% 65.29% +3.74%
3 2026-05-01 — 61.55% —

Full EPSS history (23 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-60787

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-60787

GitHub Security Advisory for CVE-2025-60787

GHSA-j945-qm58-4gjx · Severity: high · Ecosystem: pip — motionEye vulnerable to RCE via unsanitized motion config parameter

Affected software / configurations for CVE-2025-60787

Vendor Product Version Raw CPE
motioneye_project motioneye 0.42.1 cpe:2.3:a:motioneye_project:motioneye:0.42.1:*:*:*:*:*:*:*
motioneye_project motioneye 0.43.1 cpe:2.3:a:motioneye_project:motioneye:0.43.1:beta1:*:*:*:*:*:*
motioneye_project motioneye 0.43.1 cpe:2.3:a:motioneye_project:motioneye:0.43.1:beta2:*:*:*:*:*:*
motioneye_project motioneye 0.43.1 cpe:2.3:a:motioneye_project:motioneye:0.43.1:beta3:*:*:*:*:*:*
motioneye_project motioneye 0.43.1 cpe:2.3:a:motioneye_project:motioneye:0.43.1:beta4:*:*:*:*:*:*

References for CVE-2025-60787

cvelogic Threat Intelligence