CVE-2026-100372

Multiple SQL injection vulnerabilities in the update_counter function in includes/functions.php in ClipBucket 2.6 allow remote attackers to execute arbitrary SQL commands via the time parameter to videos.php or channels.php.

ClipBucket V5's web installer fails to properly validate or escape the php_cli_filepath parameter before passing it to shell execution. Unauthenticated attackers can submit a crafted POST request to the installer with a malicious php_cli_filepath value to execute arbitrary commands as the web server user.

ClipBucket v5 is an open source video sharing platform. Prior to version 5.5.3 - #140, the Remote Play feature allowed adding videos by importing an external URL, leading to arbitrary command execution due to improper URL handling.

ClipBucket v5 versions 5.5.2-#187 and below allow an attacker to perform Blind SQL Injection through the add comment section within a channel. The obj_id parameter in the POST request to /actions/ajax.php is used within the user_exists function of the upload/includes/classes/user.class.php file as the $id parameter, and then used within the count function of the upload/includes/classes/db.class.php file. The $id parameter is concatenated into the query without validation or sanitization, and user-supplied input like 1' or 1=1-- - can trigger the injection. This issue does not have a fix at the time of publication.

ClipBucket 5.5.2 is shipped with hardcoded default administrative credentials. An unauthenticated remote attacker can log in to the admin panel, gaining full administrative control of the application.

Blind SQL injection vulnerability in ClipBucket v5 before 5.5.3-#182 in the photo search endpoint where the query parameter is passed unsanitized into SQL WHERE and ORDER BY clauses. Unauthenticated attackers can exploit time-based blind SQL injection to extract credentials and admin password hashes.

ClipBucket v5 before 5.5.3-#182 contains a reflected cross-site scripting vulnerability in the sort_link() helper function that fails to sanitize cat, sort, and time query parameters. Attackers can craft malicious requests with injected script payloads in these parameters to execute arbitrary JavaScript in victims' browsers under the application origin.

ClipBucket v5 before 5.5.3-#182 contains a file upload vulnerability that allows authenticated users to achieve remote code execution by uploading a PHP file with valid image magic bytes through the photo upload endpoint. The FileUpload::manageFile() function fails to update the file extension after MIME validation, allowing a .php extension to persist and execute via PHP-FPM.

ClipBucket v5 before 5.5.3-#182 contains a blind SQL injection vulnerability. An authenticated user can submit the msg_id parameter as an array to bypass the clean_requests() sanitization function in ClipBucket.class.php, then inject the unsanitized message ID into a SQL query in cb_pm::delete_msg().

ClipBucket v5 before 5.5.3-#182 contains a blind SQL injection vulnerability. An authenticated user can submit the check_photo parameter as an array to bypass the clean_requests() sanitization function in ClipBucket.class.php, then inject unsanitized values into a SQL query in photo_exists() in photos.class.php.