Vulnerability in motioneye (CVE-2025-60787)
Summary
Vulnerability in motioneye (CVE-2025-60787). Successful exploitation can lead to full system takeover. Exploitable via image_file_name. Mitigation: upgrade to 0.43.1b5 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-60787 has been found in motioneye.
Attackers can target a specific entry point like image_file_name over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: upgrade motioneye to 0.43.1b5 or later.
If unsure, ask your IT team or search "motioneye CVE-2025-60787" on the vendor's site.
CVE-2025-60787 (motioneye) — CWE-116 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: image_file_name / motion
Patched: 0.43.1b5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-116) exists in motioneye. Attackers reach the vulnerable code path via image_file_name.
Check the vendor advisory for the affected versions of motioneye. Attack surface: image_file_name / motion.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to 0.43.1b5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'motioneye' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'motioneye' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
motioneyeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade motioneye to 0.43.1b5ステージング環境で 0.43.1b5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package github.com
- package pypi.org
- web github.com