High Input validation exploit reference

CVE-2025-60787 — motionEye vulnerable to RCE via unsanitized motion config parameter

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 Oct 3, 2025 · Updated Oct 25, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: mitre

High

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

Metasploit modules · 1 Exploit-DB · 1

How the score was calculated

Public exploit/PoC (metasploit, exploitdb)+20
EPSS 18.5% (30-day exploitation probability)+15
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

18.46%

ahead of 97% of scored CVEs · Oct 30, 2026

Affects

Motioneye-project

Motioneye

CVSS base

7.2

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Pip Motioneye: fixed in version 0.43.1b5 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Motioneye-project Motioneye, Pip Motioneye).
Apply the fixed version or the patch documented under Remediation.
EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Motioneye-project	Motioneye	version 0.42.1version 0.43.1-beta1version 0.43.1-beta2version 0.43.1-beta3version 0.43.1-beta4	Vulnerable	NIST National Vulnerability Database
Pip	Motioneye	< 0.43.1b5	Vulnerable	GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.2	CVSS 3.1	High	1.2	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.2	CVSS 3.1	High	—	—	GitHub, Inc. via GitHub Security Advisories
7.2	CVSS 3.1	High	—	—	CISA-ADP via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules

Remote Code Execution Vulnerability in MotionEye Frontend (CVE-2025-60787) excellent Sep 9, 2025

Exploit-DB

motionEye 0.43.1b4 - RCE Feb 11, 2026

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 25, 2026 → Oct 30, 2026 · 6 reading(s) · max 18.46%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Fix documented
Oct 25, 2026 · GitHub Security Advisories
Affected products added · pip/motioneye
Oct 25, 2026 · GitHub Security Advisories
Affected products added · motioneye project/motioneye
Oct 25, 2026 · NIST National Vulnerability Database
Source status changed · Published → Modified
Oct 25, 2026 · NIST National Vulnerability Database
Record published
Oct 25, 2026
CVSS changed · 7.2
Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Published
Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 25, 2026 · CVE Program (cve.org) e CISA ADP
Record created in this database
Oct 25, 2026 · Alertas do Telegram
2025
CVE published
Oct 3, 2025 · mitre

Source activity

Repeated readings are counted rather than listed.

2× References added · Oct 25, 2026 – Oct 25, 2026
1× Official description updated · Oct 25, 2026 – Oct 25, 2026

References

4 on the record

nvd.nist.gov/vuln/detail/CVE-2025-60787
GitHub Security Advisories
github.com/prabhatverma47/motionEye-RCE-through-config-parameter
Exploit, Third Party Advisory, CVE Program (cve.org) e CISA ADP
github.com/advisories/GHSA-j945-qm58-4gjx
GitHub Security Advisories
github.com/motioneye-project/motioneye/security/advisories/GHSA-j945-qm58-4gjx
GitHub Security Advisories

Elsewhere on this site

Motioneye-project
every CVE for this vendor

Input validation
same class

CWE-20
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-55863 motionEye: Missing authentication on ActionHandler allows unauthenticated camera action execution Sep 15, 2026
Critical CVE-2026-46488 motionEye: Authentication possible via password hash Sep 15, 2026
Medium CVE-2026-31978 motionEye: Arbitrary File Read via Path Traversal in Picture/Movie Preview Endpoint Jun 24, 2026
Medium CVE-2026-32315 motionEye: World-Readable Configuration File Exposes Admin Password Hash Jun 24, 2026
High CVE-2026-55488 motionEye's Absolute Path Traversal in Media File Handlers Allows Arbitrary File Read Jun 24, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-60787 is "motionEye vulnerable to RCE via unsanitized motion config parameter", rated High. It affects Motioneye (Motioneye-project); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 18.46% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.