{"answers":{"affected":"3 open source packages ship an affected version, including motioneye. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60787 exists.","fix":"Upgrade motioneye to 0.43.1b5 or later.","what":"CVE-2025-60787 is a high-severity command injection vulnerability in n/a, published on 3 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-60787 and fix it if it is affected.\n\nWhat it is: CVE-2025-60787 is a high-severity command injection vulnerability in n/a, published on 3 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60787 exists.\n\nAffected packages and fixed versions:\n- motioneye (PyPI): affected all versions; fixed in 0.43.1b5\n- motioneye (PyPI): affected all versions; fixed in 0.43.1b5\n- motioneye (PyPI): affected all versions; fixed in 0.43.1b5\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-60787/ (Markdown: https://insights.sbomify.com/CVE-2025-60787/index.md)","id":"CVE-2025-60787","markdown":"https://insights.sbomify.com/CVE-2025-60787/index.md","name":"CVE-2025-60787","record":{"aliases":["GHSA-j945-qm58-4gjx","PYSEC-2026-1680"],"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":"high_privilege","summary":"Authenticated administrators can execute arbitrary OS commands via unsanitized configuration parameters in MotionEye.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"motioneye","vendor":"motioneye_project"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as image_file_name. Unsanitized user input is written to Motion configuration files, allowing remote authenticated attackers with admin access to achieve code execution when Motion is restarted.","ecosystems":["PyPI"],"exploits":{"exploitdb":1,"first_seen":"2025-09-09","github_poc":9,"max_poc_stars":10,"metasploit":1,"nuclei":0,"refs":[{"date":"2026-03-08T01:47:37Z","kind":"github_poc","ref":"https://github.com/gunzf0x/CVE-2025-60787","stars":10,"title":"PoC for CVE-2025-60787 - Authenticated RCE in motionEye for all versions up to 0.43.1b4 (included)"},{"date":"2026-03-08T04:01:24Z","kind":"github_poc","ref":"https://github.com/lil0xplorer/CVE-2025-60787_PoC","stars":2,"title":null},{"date":"2026-03-07T08:45:30Z","kind":"github_poc","ref":"https://github.com/Rohitberiwala/CVE-2025-60787-MotionEye-RCE","stars":1,"title":"Professional PoC for CVE-2025-60787: Remote Code Execution in MotionEye (\u003c= 0.43.1b4). This exploit demonstrates an OS Command Injection vulnerability through client-side validation bypass, allowing attackers to execute arbitrary commands via configuration files."},{"date":"2025-09-09","kind":"metasploit","ref":"exploit/linux/http/motioneye_auth_rce_cve_2025_60787","stars":null,"title":"Remote Code Execution Vulnerability in MotionEye Frontend (CVE-2025-60787)"},{"date":"2025-10-03T15:20:43Z","kind":"github_poc","ref":"https://github.com/prabhatverma47/CVE-2025-60787","stars":0,"title":"CVE-2025-60787 Poc - RCE - MotionEye \u003c= 0.43.1b4"},{"date":"2026-02-11","kind":"exploitdb","ref":"52481","stars":null,"title":"motionEye 0.43.1b4 - RCE"},{"date":"2026-02-28T20:59:46Z","kind":"github_poc","ref":"https://github.com/GarethMSheldon/CVE-2025-60787-Detection-motionEye-RCE-via-Config-Injection","stars":0,"title":null},{"date":"2026-03-13T17:59:09Z","kind":"github_poc","ref":"https://github.com/d3vn0mi/CVE-2025-60787-POC","stars":0,"title":"Python PoC for CVE-2025-60787, authenticated OS command injection RCE in motionEye \u003c= 0.43.1b4 via unsanitized image_file_name config"}],"tier":"weaponised"},"has_fix":true,"headline":"motionEye vulnerable to RCE via unsanitized motion config parameter","id":"CVE-2025-60787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"ProcessWire CMS vulnerable to resource-exhaustion Denial of Service","id":"CVE-2025-60790"},"packages":[{"ecosystem":"PyPI","fixed":["0.43.1b5"],"introduced":["0"],"last_affected":[],"package":"motioneye","purl":null,"source":"GHSA-j945-qm58-4gjx"},{"ecosystem":"PyPI","fixed":["0.43.1b5"],"introduced":["0"],"last_affected":[],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"GHSA-j945-qm58-4gjx"},{"ecosystem":"PyPI","fixed":["0.43.1b5"],"introduced":["0"],"last_affected":[],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"PYSEC-2026-1680"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-60786"},"products":["n/a"],"published":"2025-10-03","related":[{"cvss_score":7.5,"headline":"MotionEye allows attackers to access sensitive information","id":"CVE-2022-25568","kev_date_added":null,"published":"2022-03-24"},{"cvss_score":7.2,"headline":"Unrestricted Upload of File with Dangerous Type in motionEye","id":"CVE-2021-44255","kev_date_added":null,"published":"2022-01-31"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Authenticated administrators can execute arbitrary OS commands via unsanitized configuration parameters in MotionEye.","url":"https://insights.sbomify.com/CVE-2025-60787/"}