CVE-2025-47782 is a high-severity OS command injection vulnerability in motioneye (pip), affecting versions >= 0.43.1b1, < 0.43.1b4. It is fixed in 0.43.1b4.
Summary Using a constructed (camera) device path with the config/add/addcamera motionEye web API allows an attacker with motionEye admin user credentials to execute any UNIX shell code within a non-interactive shell as executing user of the motionEye instance, motion by default. function call stack post addcamera config.addcamera v4l2ctl.listresolutions utils.callsubprocess subprocess.run PoC build reproduce Run: Now, run the following script to attack motionEye: <img width="1187" alt="Image" src="https://github.com/user-attachments/assets/8e0a9bfe-8de3-4023-96d6-0e888bfe3c62" /> <img width="324" alt="Image" src="https://github.com/user-attachments/assets/04c73349-694a-4531-993e-eea765b87d0e" /> Discussion It is obvious that callsubprocess was used to execute the incoming data, resulting in a vulnerability Impact RCE Patches The vulnerability has been patch with motionEye v0.43.1b4: https://github.com/motioneye-project/motioneye/pull/3143 Workarounds Applying the following patch, replacing the literal single quotes in the created cmd string with a shlex.quoted input device: https://patch-diff.githubusercontent.com/raw/motioneye-project/motioneye/pull/3143.patch References https://github.com/motioneye-project/motioneye/issues/3142 Credit The vulnerability was discovered by Tencent YunDing Security Lab.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
pip
motioneye (>= 0.43.1b1, < 0.43.1b4)motioneye → 0.43.1b4 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's Application Detection and Response identifies whether CVE-2025-47782 is reachable in your applications. Explore runtime application protection for your team.
See if CVE-2025-47782 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2025-47782 in your environment →Upgrade motioneye to 0.43.1b4 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2025-47782 is a high-severity OS command injection vulnerability in motioneye (pip), affecting versions >= 0.43.1b1, < 0.43.1b4. It is fixed in 0.43.1b4. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
motioneye (pip) versions >= 0.43.1b1, < 0.43.1b4 is affected.
Yes. CVE-2025-47782 is fixed in 0.43.1b4. Upgrade to this version or later.
Whether CVE-2025-47782 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade motioneye to 0.43.1b4 or later.