CVE-2025-47782: motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution

CVE-2025-47782 · Severity: medium · CVSS 4 · Published 2025-05-14

motionEye is an online interface for the software motion, a video surveillance program with motion detection. In versions 0.43.1b1 through 0.43.1b3, using a constructed (camera) device path with the `add`/`add_camera` motionEye web API allows an attacker with motionEye admin user credentials to execute any command within a non-interactive shell as motionEye run user, `motion` by default. The vulnerability has been patched with motionEye v0.43.1b4. As a workaround, apply the patch manually.

Technologies: motioneye (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-47782 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-47782 being exploited in the wild.
How severe is CVE-2025-47782?
Medium severity, with a CVSS score of 4, published 14 May 2025.
Which products and versions are affected?
motioneye (PyPI) ECOSYSTEM:introduced=0.43.1b1,fixed=0.43.1b4.
Is there a fix for CVE-2025-47782?
Yes. motioneye (PyPI): upgrade to 0.43.1b4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-47782?
Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • motioneye (PyPI): upgrade to 0.43.1b4 or later
    pip install "motioneye>=0.43.1b4"

Affected products

  • motioneye (PyPI) ECOSYSTEM:introduced=0.43.1b1,fixed=0.43.1b4

Identifiers

  • CVE-2025-47782
  • GHSA-g5mq-prx7-c588
  • PYSEC-2025-39

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.