Subscriptions
Tracking
Sign in to view the affected projects.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 27 Jan 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oxygenz
Oxygenz clipbucket |
|
| CPEs | cpe:2.3:a:oxygenz:clipbucket:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Oxygenz
Oxygenz clipbucket |
Thu, 08 Jan 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 08 Jan 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Clipbucket
Clipbucket clipbucket |
|
| Vendors & Products |
Clipbucket
Clipbucket clipbucket |
Thu, 08 Jan 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | ClipBucket v5 Vulnerable to Blind SQL Injection through Channel Comments | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-08T19:13:03.740Z
Reserved: 2026-01-05T16:44:16.369Z
Link: CVE-2026-21875
Updated: 2026-01-08T19:12:53.738Z
Status : Analyzed
Published: 2026-01-08T00:16:00.457
Modified: 2026-01-27T19:05:52.837
Link: CVE-2026-21875
No data.
OpenCVE Enrichment
Updated: 2026-01-08T09:47:41Z