LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-21875 is a critical database injection flaw in ClipBucket v5 channel comments. An unauthenticated remote attacker may be able to manipulate database queries through a comment request, risking data theft, data changes, or service disruption. The advisory states no fix was available at publication.

Executive priority

Treat this as urgent for any public ClipBucket v5 deployment. The vulnerability can affect confidentiality, integrity, and availability, and no fix was named in the source at publication. Reduce exposure while monitoring the vendor advisory for remediation.

Technical view

ClipBucket v5 versions 5.5.2-#187 and below are affected. The vulnerable flow is channel comment submission to /actions/ajax.php, where obj_id reaches user_exists and db count logic without proper validation or sanitization. This is classified as CWE-89 blind SQL injection with CVSS 3.1 score 9.8.

Likely exposure

Exposure is likely for internet-facing ClipBucket v5 sites running version 5.5.2-#187 or earlier with channel comment functionality reachable by unauthenticated users. The source does not identify hosted services, default deployments, or confirmed affected forks beyond MacWarrior clipbucket-v5.

Exploitation context

The CVE record and GitHub advisory describe a network-accessible, low-complexity, unauthenticated issue requiring no user interaction. The provided sources do not state active exploitation, public exploit availability, or inclusion in CISA KEV.

Researcher notes

Evidence is limited to the CVE data and GitHub security advisory. The root cause is unsanitized use of obj_id in database query construction during channel comment handling. Do not assume exploit activity or patch availability beyond the cited sources.

Mitigation direction

  • Check the GitHub advisory and vendor project for updated remediation guidance.
  • Identify and prioritize all ClipBucket v5 deployments at or below 5.5.2-#187.
  • Restrict external access to affected ClipBucket instances where business feasible.
  • Limit or disable channel comment functionality if supported by your deployment.
  • Increase monitoring for unusual database errors or abnormal comment activity.

Validation and detection

  • Inventory ClipBucket v5 version and build number across environments.
  • Confirm whether channel comment submission is reachable from untrusted networks.
  • Review application logs for suspicious requests to /actions/ajax.php.
  • Check database logs for malformed or abnormal queries tied to comment activity.
  • Track vendor advisory updates for a fixed version or official workaround.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21875 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-21875Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MacWarriorclipbucket-v5<= 5.5.2-#187Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.