{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-21624 exists.","fix":"No fix has been published for CVE-2025-21624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-21624 is a critical vulnerability in MacWarrior clipbucket-v5, published on 7 Jan 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-21624 and fix it if it is affected.\n\nWhat it is: CVE-2025-21624 is a critical vulnerability in MacWarrior clipbucket-v5, published on 7 Jan 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-21624 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-21624/ (Markdown: https://insights.sbomify.com/CVE-2025-21624/index.md)","id":"CVE-2025-21624","markdown":"https://insights.sbomify.com/CVE-2025-21624/index.md","name":"CVE-2025-21624","record":{"aliases":["GHSA-98vm-2xqm-xrcc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ClipBucket video hosting","requires_auth":"none","summary":"Attackers can upload malicious PHP scripts via playlist covers to execute arbitrary code on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"clipbucket","vendor":"oxygenz"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"ClipBucket V5 provides open source video hosting with PHP. Prior to 5.5.1 - 239, a file upload vulnerability exists in the Manage Playlist functionality of the application, specifically surrounding the uploading of playlist cover images. Without proper checks, an attacker can upload a PHP script file instead of an image file, thus allowing a webshell or other malicious files to be stored and executed on the server. This attack vector exists in both the admin area and low-level user area. This vulnerability is fixed in 5.5.1 - 239.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"ClipBucket V5 Playlist Cover File Upload to Remote Code Execution","id":"CVE-2025-21624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"GLPI vulnerable to exposure of sensitive information in the `status.php` endpoint","id":"CVE-2025-21626"},"packages":[],"prev":{"headline":"ClipBucket V5 Unauthenticated Template Directory Update to Denial-of-Service","id":"CVE-2025-21623"},"products":["clipbucket-v5"],"published":"2025-01-07","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":"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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-07","vendors":["MacWarrior"]},"summary":"Attackers can upload malicious PHP scripts via playlist covers to execute arbitrary code on the server.","url":"https://insights.sbomify.com/CVE-2025-21624/"}