Skip to main content
CVE-2026-21875VulnerabilityPublished

CVE-2026-21875: MacWarrior clipbucket-v5 · SQL Injection

Affects MacWarrior clipbucket-v5Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jan 2026

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
MacWarriorclipbucket-v5Affected
  • =<= 5.5.2-#187
Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should immediately implement the following mitigations: 1) Apply strict input validation and sanitization on the obj_id parameter and any other user-supplied inputs, rejecting suspicious or malformed data. 2) Modify the source code to use parameterized queries or prepared statements instead of direct string concatenation for SQL commands, eliminating injection vectors. 3) Employ Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection patterns targeting ClipBucket endpoints. 4) Restrict access to the /actions/ajax.php endpoint via network segmentation or IP whitelisting where feasible. 5) Monitor application logs and database query logs for anomalous patterns indicative of injection attempts. 6) Conduct thorough security audits and penetration testing focusing on injection flaws. 7) Prepare incident response plans for potential exploitation scenarios. 8) Engage with the ClipBucket community or vendor for updates or unofficial patches. 9) Consider temporary disabling of the comment feature if it is not critical to operations until a fix is available. 10) Educate developers and administrators on secure coding practices to prevent similar vulnerabilities.

Description

ClipBucket v5 is an open source video sharing platform. Versions 5.5.2-#187 and below allow an attacker to perform Blind SQL Injection through the add comment section within a channel. When adding a comment within a channel, there is a POST request to the /actions/ajax.php endpoint. The obj_id parameter within the POST request to /actions/ajax.php is then used within the user_exists function of the upload/includes/classes/user.class.php file as the $id parameter. It is 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 a user-supplied input like 1' or 1=1-- - can be used to trigger the injection. This issue does not have a fix at the time of publication.

References

Community reviews

Loading reviews…