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

Advisory record · `GHSA-g5mq-prx7-c588`

- **Identifiers:** `GHSA-g5mq-prx7-c588` · `CVE-2025-47782` · `PYSEC-2025-39`
- **State:** Confirmed
- **Severity:** CVSS 8.9 High
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md)
- **Published:** 15 May 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `motioneye` (PyPI): affected `>=0.43.1b1, <0.43.1b4`; fixed in `0.43.1b4`

## 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

- 8.9 High, CVSS 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`, from 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

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g5mq-prx7-c588)

## Sources

- [GitHub Advisory Database: GHSA-g5mq-prx7-c588](https://github.com/advisories/GHSA-g5mq-prx7-c588)
- [OSV: GHSA-g5mq-prx7-c588](https://osv.dev/vulnerability/GHSA-g5mq-prx7-c588)
- <https://github.com/motioneye-project/motioneye/security/advisories/GHSA-g5mq-prx7-c588>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-47782>
- <https://github.com/motioneye-project/motioneye/issues/3142>
- <https://github.com/motioneye-project/motioneye/pull/3143>
- <https://github.com/motioneye-project/motioneye>
- <https://github.com/pypa/advisory-database/tree/main/vulns/motioneye/PYSEC-2025-39.yaml>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g5mq-prx7-c588>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g5mq-prx7-c588/>. Everything for agents: <https://agentprime.io/llms.txt>.
