Summary
ClipBucket v5 contains an SQL injection flaw in the subtitle title editing endpoint, where an authenticated uploader can manipulate a numeric parameter to inject SQL logic.
Under typical deployments, this may allow a malicious user to perform boolean-based blind SQL injection to exfiltrate sensitive information from the application's database.
Affected context
The vulnerability occurs in ClipBucket v5 instances where authenticated users are allowed to upload videos and manage subtitles.
Specifically, the /actions/subtitle_edit.php endpoint processes a number parameter from POST requests without robust validation or safe query construction.
Environments that grant broad access to video upload features or share accounts among multiple users are more exposed to this issue, as it increases the pool of potential attackers.
Exploit preconditions
- Attack surface: Web application endpoint
/actions/subtitle_edit.php, reachable over HTTP(S). - Required access: Authenticated user account with permission to upload videos and manage subtitles.
- Trigger point: Submission of a crafted
numberparameter in the subtitle title edit POST request. - Why exploitation is possible: The
numberparameter is incorporated into SQL statements in an unsafe manner, allowing an attacker to alter query logic and perform boolean-based blind SQL injection.
Why this happens
The root cause is the construction of SQL queries using untrusted input from the number parameter without proper parameterization or rigorous validation.
This aligns with CWE-89: SQL Injection, where user-controlled data is concatenated into SQL commands, enabling attackers to inject additional predicates or subqueries.
The subtitle editing functionality treats a value that appears numeric as inherently safe, but the absence of strict typing or prepared statements allows crafted payloads to influence database behavior.
Potential impact
- Unauthorized reading of sensitive data from the application database (user records, email addresses, or other stored information).
- Enumeration of database structure, including table and column names.
- Potential escalation to broader database compromise if combined with other misconfigurations.
- Indirect impact on privacy and regulatory compliance due to exposure of stored user data.
General mitigation guidance
Mitigation typically focuses on enforcing strict separation between user input and SQL query logic.
Pattern-based controls include:
- Using parameterized queries or prepared statements for all database interactions, especially where user-controlled parameters select or filter records.
- Applying strict server-side validation for parameters expected to be numeric, rejecting any value that does not match a constrained numeric format.
- Centralizing database access patterns behind a data access layer that enforces safe query construction by default.
- Limiting the amount of sensitive data stored and segmenting data access by role, so that compromised queries have reduced reach.
How teams detect issues like this
Detection efforts can combine code-centric and operational approaches:
- Static analysis rules targeting string-concatenated SQL, especially around request parameters like
numberin subtitle editing modules. - Manual code review focusing on areas where user input is used to build WHERE clauses, ORDER BY expressions, or dynamic table/column references.
- Database audit logging and monitoring for abnormal query patterns, such as repetitive boolean-based probing or unusual predicates.
- Policy enforcement in CI/CD pipelines to block changes that introduce ad-hoc SQL construction without parameterization.

