{"answers":{"affected":"3 open source packages ship an affected version, including motioneye.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47782 exists.","fix":"Upgrade motioneye to 0.43.1b4 or later.","what":"CVE-2025-47782 is a high-severity command injection vulnerability in motioneye-project motioneye, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47782 and fix it if it is affected.\n\nWhat it is: CVE-2025-47782 is a high-severity command injection vulnerability in motioneye-project motioneye, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47782 exists.\n\nAffected packages and fixed versions:\n- motioneye (PyPI): affected from 0.43.1b1; fixed in 0.43.1b4\n- motioneye (PyPI): affected from 0.43.1b1; fixed in 0.43.1b4\n- motioneye (PyPI): affected from 0.43.1b1; fixed in 0.43.1b4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47782/ (Markdown: https://insights.sbomify.com/CVE-2025-47782/index.md)","id":"CVE-2025-47782","markdown":"https://insights.sbomify.com/CVE-2025-47782/index.md","name":"CVE-2025-47782","record":{"aliases":["GHSA-g5mq-prx7-c588","PYSEC-2025-39"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"motionEye web interface","requires_auth":"none","summary":"An authenticated admin can execute arbitrary commands via the add_camera API due to unsafe command execution in motionEye.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"motionEye vulnerable to RCE in add_camera Function Due to unsafe command execution","id":"CVE-2025-47782","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"label-studio vulnerable to Cross-Site Scripting (Reflected) via the label_config parameter.","id":"CVE-2025-47783"},"packages":[{"ecosystem":"PyPI","fixed":["0.43.1b4"],"introduced":["0.43.1b1"],"last_affected":[],"package":"motioneye","purl":null,"source":"GHSA-g5mq-prx7-c588"},{"ecosystem":"PyPI","fixed":["0.43.1b4"],"introduced":["0.43.1b1"],"last_affected":[],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"GHSA-g5mq-prx7-c588"},{"ecosystem":"PyPI","fixed":["0.43.1b4"],"introduced":["0.43.1b1"],"last_affected":[],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"PYSEC-2025-39"}],"prev":{"headline":"Rallly Insufficient Password Login Token Entropy Leads to Account Takeover","id":"CVE-2025-47781"},"products":["motioneye"],"published":"2025-05-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-14","vendors":["motioneye-project"]},"summary":"An authenticated admin can execute arbitrary commands via the add_camera API due to unsafe command execution in motionEye.","url":"https://insights.sbomify.com/CVE-2025-47782/"}