Security readout for executives and security teams
Plain-English summary
MotionEye versions v0.43.1b4 and earlier are reported vulnerable to command injection through configuration values. An authenticated administrator could place unsafe input into settings that MotionEye writes into Motion configuration files, leading to code execution when Motion restarts.
Executive priority
Prioritize remediation for any exposed or shared-admin MotionEye deployments. The requirement for admin privileges lowers broad internet risk, but successful abuse can produce full code execution on the host.
Technical view
The CVE describes improper input handling and output encoding in configuration parameters such as image_file_name. The flaw maps to CWE-20, CWE-116, and CWE-78, with CVSS 3.1 score 7.2. Exploitation requires network access and high privileges, but no user interaction.
Likely exposure
Exposure is most likely in MotionEye deployments at v0.43.1b4 or earlier where admin access is reachable over the network. The CVE metadata does not provide vendor CPEs or a complete affected-product matrix.
Exploitation context
The source bundle includes a public GitHub reference, but CISA KEV is false and no cited source states active exploitation. The described attacker must already have authenticated admin access and execution occurs when Motion is restarted.
Researcher notes
Evidence is limited to CVE metadata and the linked public repository. No official patch, commit, or vendor advisory is named in the provided sources, so remediation should be validated against current MotionEye maintainer guidance.
Mitigation direction
- Check MotionEye project guidance for a fixed release or official mitigation.
- Restrict MotionEye admin access to trusted users and networks.
- Review admin accounts and rotate credentials if compromise is suspected.
- Inspect Motion configuration values for unexpected or unsafe content.
- Avoid restarting Motion until configuration integrity is reviewed.
Validation and detection
- Inventory MotionEye instances and record deployed versions.
- Identify systems running v0.43.1b4 or earlier.
- Confirm whether admin interfaces are network-accessible.
- Review recent configuration changes by admin users.
- Check logs around Motion restarts for suspicious behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-116: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-60787 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/prabhatverma47/motionEye-RCE-through-config-parameterCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.