CVE-2025-60787

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 19.0%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Weaponized
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 19%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
58(Track*)
EG Risk 58/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation65% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
97.0%
KEV
Not listed

Published

October 3, 2025

Last Modified

July 5, 2026

Advisory Details (1)

Auto-updated Jul 7, 2026
Patch available.
generic Patch Available

GitHub - prabhatverma47/motionEye-RCE-through-config-parameter: PoC steps for this vulnerability · GitHub

https://github.com/prabhatverma47/motionEye-RCE-through-config-parameter

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
motioneye0.27 ... 0.43.1b4 (60 versions)0.43.1b5—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:00 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-13 22:29 UTCEPSS rescore
  16. 2026-07-13 06:12 UTCEPSS rescore
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:09 UTCEPSS rescore
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 13:11 UTCOSV refresh
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 51 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-04 06:30 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:55 UTCEPSS rescore
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-24 14:04 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-23 21:32 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 01:13 UTCOSV refresh
  26. 2026-06-17 17:52 UTCEPSS rescore
  27. 2026-06-16 17:52 UTCEPSS rescore
  28. 2026-06-15 17:48 UTCEPSS rescore
  29. 2026-06-15 17:48 UTCEPSS rescore
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-13 23:00 UTCEPSS rescore
  32. 2026-06-12 23:11 UTCEPSS rescore
  33. 2026-06-11 14:00 UTCEPSS rescore
  34. 2026-06-10 22:18 UTCEPSS rescore
  35. 2026-06-10 22:18 UTCEPSS rescore
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-05 22:46 UTCEPSS rescore
  40. 2026-06-05 22:46 UTCEPSS rescore
  41. 2026-06-05 06:10 UTCEPSS rescore
  42. 2026-06-05 06:10 UTCEPSS rescore
  43. 2026-06-02 20:13 UTCEPSS rescore
  44. 2026-06-02 20:12 UTCEPSS rescore
  45. 2026-06-01 13:51 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-29 21:35 UTCEG score recompute
  50. 2026-05-29 15:57 UTCOSV refresh
  51. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCgunzf0x/CVE-2025-60787
    First seen Mar 8, 2026

    PoC for CVE-2025-60787 - Authenticated RCE in motionEye for all versions up to 0.43.1b4 (included)

    Open source ↗
  • GitHub PoClil0xplorer/CVE-2025-60787_PoC
    First seen Mar 8, 2026
    Open source ↗
  • Exploit-DBEDB-52481
    First seen Feb 11, 2026

    motionEye 0.43.1b4 - RCE

    Open source ↗
  • Metasploitexploit/linux/http/motioneye_auth_rce_cve_2025_60787✓ verified
    First seen Sep 9, 2025

    Remote Code Execution Vulnerability in MotionEye Frontend (CVE-2025-60787)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-60787?
CVE-2025-60787 is a high vulnerability published on October 3, 2025. MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as imagefilename. Unsanitized user input is written to Motion configuration files, allowing remote authenticated attackers with admin access to achieve code execution when Motion is restarted.
When was CVE-2025-60787 disclosed?
CVE-2025-60787 was first published in the National Vulnerability Database on October 3, 2025, with the most recent update on July 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-60787 actively exploited?
CVE-2025-60787 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-60787?
CVE-2025-60787 has a CVSS v3.1 base score of 7.2 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-60787?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-60787, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-60787

Explore →

Is Your Infrastructure Affected by CVE-2025-60787?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs