motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| motioneye-project | motioneye | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Motioneye Project | Motioneye | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-14950 | motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution |
Github GHSA |
GHSA-g5mq-prx7-c588 | motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.508% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution | |
| Weaknesses | CWE-78 | |
| References |
| |
| Metrics |
cvssV4_0
|