Advisory record · GHSA-g5mq-prx7-c588

motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution

CVSS 8.9 HighEPSS 0.0052 · 44th percentile

Published by the GitHub Advisory Database at 15 May 2025, 16:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
motioneyePyPI>=0.43.1b1, <0.43.1b40.43.1b4
Identifiers
GHSA-g5mq-prx7-c588 · CVE-2025-47782 · PYSEC-2025-39
Weakness (CWE)
CWE-78
Published
15 May 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

motionEye versions >=0.43.1b1 and <0.43.1b4 are vulnerable to remote code execution through the add_camera function, which runs unsanitized device path input in a subprocess. An attacker with motionEye admin credentials could execute arbitrary shell commands as the user running motionEye, which is motion by default. Upgrade to motionEye 0.43.1b4, which fixes the issue.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.9 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0052, the 44th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:29 UTC First seen by agentprime
  2. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.