# CVE-2026-21875: ClipBucket v5 Vulnerable to Blind SQL Injection through Channel Comments

> Attackers can execute blind SQL injection via the channel comment feature to read or modify database contents in ClipBucket v5.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-crpv-fmc4-j392

## What is CVE-2026-21875?

CVE-2026-21875 is a critical SQL injection vulnerability in MacWarrior clipbucket-v5, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-21875?

It affects 1 product.


Products: Oxygenz Clipbucket.

## How do I fix CVE-2026-21875?

No fix has been published for CVE-2026-21875 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-21875 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21875 exists.

Public exploit code:

- ClipBucket v5 <= 5.5.2 - Unauthenticated Blind SQL Injection (nuclei): http/cves/2026/CVE-2026-21875.yaml

## Other vulnerabilities in MacWarrior clipbucket-v5

- [CVE-2025-67418](https://insights.sbomify.com/CVE-2025-67418/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-21624](https://insights.sbomify.com/CVE-2025-21624/): ClipBucket V5 Playlist Cover File Upload to Remote Code Execution (critical 9.8)
- [CVE-2024-54135](https://insights.sbomify.com/CVE-2024-54135/): Untrusted Deserialization in ClipBucket-v5 Version 2.0 to 5.5.1 Revision 199 (critical 9.8)
- [CVE-2024-54136](https://insights.sbomify.com/CVE-2024-54136/): Untrusted Deserialization in ClipBucket-v5 Version 5.5.1 Revision 199 and Below (critical 9.8)
- [CVE-2026-25728](https://insights.sbomify.com/CVE-2026-25728/): ClipBucket v5 Affected by Remote Code Execution via Avatar/Background File Upload Race Condition (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21875 and fix it if it is affected.

What it is: CVE-2026-21875 is a critical SQL injection vulnerability in MacWarrior clipbucket-v5, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21875 exists.

Affected product: MacWarrior clipbucket-v5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-21875/ (Markdown: https://insights.sbomify.com/CVE-2026-21875/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-21875
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21875
- OSV: https://osv.dev/vulnerability/CVE-2026-21875

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-21875/
Summaries are generated and may contain mistakes; the official description above is the record.