← Back
CVE-2025-60787
high
CVSS 7.2
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-116) exists in motioneye. Attackers reach the vulnerable code path via ``image_file_name`` without authentication.
📍 Affected scope
motioneye — . Attack surface: `image_file_name` / `motion`.
🔥 Severity
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.43.1b5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade motioneye to 0.43.1b5ステージング環境で 0.43.1b5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
motioneye
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.43.1b5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-60787
- advisory https://github.com/advisories/GHSA-j945-qm58-4gjx
- package https://github.com/motioneye-project/motioneye
- package https://pypi.org/project/motioneye
- web https://github.com/prabhatverma47/motionEye-RCE-through-config-parameter
- web https://github.com/motioneye-project/motioneye/security/advisories/GHSA-j945-qm58-4gjx