{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62429 exists.","fix":"No fix has been published for CVE-2025-62429 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62429 is a high-severity code injection vulnerability in MacWarrior clipbucket-v5, published on 20 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62429 and fix it if it is affected.\n\nWhat it is: CVE-2025-62429 is a high-severity code injection vulnerability in MacWarrior clipbucket-v5, published on 20 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-62429 exists.\n\nAffected product: MacWarrior clipbucket-v5. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-62429/ (Markdown: https://insights.sbomify.com/CVE-2025-62429/index.md)","id":"CVE-2025-62429","markdown":"https://insights.sbomify.com/CVE-2025-62429/index.md","name":"CVE-2025-62429","record":{"aliases":["GHSA-3x4g-x3gv-rjmq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ClipBucket video platform","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary PHP code via the update launch action, leading to remote code execution on ClipBucket v5 installations.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"clipbucket","vendor":"oxygenz"}],"cvss":{"score":7.2,"severity":"high","source":"cna","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-94","name":"Improper Control of Generation of Code"}],"description":"ClipBucket v5 is an open source video sharing platform. Prior to version 5.5.2 #147, ClipBucket v5 is vulnerable to arbitrary PHP code execution. In /upload/admin_area/actions/update_launch.php, the \"type\" parameter from a POST request is embedded into PHP tags and executed. Proper sanitization is not performed, and by injecting malicious code an attacker can execute arbitrary PHP code. This allows an attacker to achieve RCE. This issue has been resolved in version 5.5.2 #147.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-31","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-31T13:05:30Z","kind":"github_poc","ref":"https://github.com/drkim-dev/CVE-2025-62429","stars":1,"title":"CVE-2025-62429 | clipbucket RCE"}],"tier":"weaponised"},"has_fix":false,"headline":"ClipBucket v5 executes arbitrary PHP code","id":"CVE-2025-62429","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"ClipBucket v5 stored XSS via video/photo fields","id":"CVE-2025-62430"},"packages":[],"prev":{"headline":"Drawing-Captcha APP Host Header Injection in `/register` and `/confirm-email` Endpoints","id":"CVE-2025-62428"},"products":["clipbucket-v5"],"published":"2025-10-20","related":[{"cvss_score":9.8,"headline":"ClipBucket v5 Vulnerable to Blind SQL Injection through Channel Comments","id":"CVE-2026-21875","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-67418","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":9.8,"headline":"ClipBucket V5 Playlist Cover File Upload to Remote Code Execution","id":"CVE-2025-21624","kev_date_added":null,"published":"2025-01-07"},{"cvss_score":9.8,"headline":"Untrusted Deserialization in ClipBucket-v5 Version 2.0 to 5.5.1 Revision 199","id":"CVE-2024-54135","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Untrusted Deserialization in ClipBucket-v5 Version 5.5.1 Revision 199 and Below","id":"CVE-2024-54136","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.3,"headline":"ClipBucket v5 Affected by Remote Code Execution via Avatar/Background File Upload Race Condition","id":"CVE-2026-25728","kev_date_added":null,"published":"2026-02-10"},{"cvss_score":8.8,"headline":"ClipBucket v5 has time-based Blind SQL Injection in ajax.php that leads to Data Exfiltration","id":"CVE-2026-32321","kev_date_added":null,"published":"2026-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-20","vendors":["MacWarrior"]},"summary":"Attackers can execute arbitrary PHP code via the update launch action, leading to remote code execution on ClipBucket v5 installations.","url":"https://insights.sbomify.com/CVE-2025-62429/"}