Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-60787: MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as image

55
This week
HIGH 7.2DOWNGRADE

CVE-2025-60787 is a high-severity flaw (CVSS 7.2) affecting motioneye. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • EPSS top 3%: very likely to be exploited
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score7.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance18.5% (top 3%)
CISA exploited listNo
WeaknessCWE-20, CWE-78, CWE-116
Published2025-10-03
Last modified2026-07-05
Publisher (CNA): MITRE · Vendor: motioneye project

Share: LinkedIn · X · Reddit

Last updated 2026-07-05 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

motioneye project motioneye DOWNGRADE
Affected: 0.42.1 · 0.43.1 beta1 · 0.43.1 beta2 · 0.43.1 beta3 · 0.43.1 beta4
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.42.1
1. Check installed version
apt-cache policy motioneye || rpm -q motioneye || motioneye --version
2. No fixed release: DOWNGRADE to a release before 0.42.1 (Debian / Ubuntu)
apt-cache madison motioneye sudo apt install motioneye=<VERSION_BEFORE_0.42.1> sudo apt-mark hold motioneye
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list motioneye sudo dnf downgrade motioneye-<VERSION_BEFORE_0.42.1> sudo dnf versionlock add motioneye
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
Python (pip) · motioneye · FIXED · 0.43.1b5 · vulnerable: < 0.43.1b5 · source
pip install --upgrade "motioneye>=0.43.1b5" pip show motioneye
Fedora 46 · pipx · FIXED · 1.18.9-1.fc46 · FEDORA-2026-95305954ab · source
sudo dnf upgrade --advisory=FEDORA-2026-95305954ab
Fedora ELN · libisds · FIXED · 0.11.2-19.eln159 · FEDORA-2026-bf61b68668 · source
sudo dnf upgrade --advisory=FEDORA-2026-bf61b68668

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-60787?

motioneye: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-60787 being exploited?

CVE-2025-60787 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-60787 affect?

CVE-2025-60787 affects motioneye. Severity is high (CVSS 7.2). 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 ac

How urgent is CVE-2025-60787?

Priority 55/100. High severity; EPSS top 3%: very likely to be exploited; Public exploit reference

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.