cve.bz

CVE-2025-60787 motioneye project motioneye: OS Command Injection

7.2 highExploitEPSS 19%Fix available

High (7.2) in motioneye project motioneye. EPSS 19% estimated probability of exploitation activity in the next 30 days. Fixed in motioneye 0.43.1b5.

On this page
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-20 Improper Input Validation
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • motioneye (PyPI): fixed in 0.43.1b5

Ask an AI about this CVE

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.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
motioneye_project:motioneye0.42.1
motioneye_project:motioneye0.43.1:beta1
motioneye_project:motioneye0.43.1:beta2
motioneye_project:motioneye0.43.1:beta3
motioneye_project:motioneye0.43.1:beta4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j945-qm58-4gjxPyPImotioneye<0.43.1b50.43.1b5
PYSEC-2026-1680PyPImotioneye<0.43.1b50.43.1b5

Public exploits

GitHub PoC

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-60787 Harbor Check: matches CVE 10 stars, Python, created
    PoC for CVE-2025-60787 - Authenticated RCE in motionEye for all versions up to 0.43.1b4 (included)
  • lil0xplorer/CVE-2025-60787_PoC Harbor Check: matches CVE 2 stars, Python, created
  • Rohitberiwala/CVE-2025-60787-MotionEye-RCE Harbor Check: matches CVE 1 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-60787 Harbor Check: matches CVE 0 stars, Python, created
    MotionEye OS Command Injection (CVE-2025-60787)
  • ozcanpng/CVE-2025-60787 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2025-60787 motionEye authenticated command injection RCE PoC
4 more

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High
  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON