SQL Injection in ClipBucket (CVE-2026-42847)
Summary
SQL injection in ClipBucket (CVE-2026-42847). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.5.3 or later.
Original description
The description as published by the source.
ClipBucket v5 is an open source video sharing platform. Prior to 5.5.3 - #122, there is a critical SQL Injection (SQLi) vulnerability in ClipBucket, exploitable through the type parameter on the authenticated admin endpoint admin_area/action_logs.php. The endpoint admin_area/action_logs.php reads $_GET['type'], stores it in $result_array['type'], and forwards it into fetch_action_logs(), where the value is concatenated directly into a SQL WHERE condition on action_type without parameterization. This allows UNION-based SQL injection and direct data exfiltration from the database. This vulnerability is fixed in 5.5.3 - #122.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42847 has been found in ClipBucket.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ClipBucket to 5.5.3 or later.
If unsure, ask your IT team or search "ClipBucket CVE-2026-42847" on the vendor's site.
CVE-2026-42847 (ClipBucket) — CWE-89
Patched: 5.5.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in ClipBucket.
Check the vendor advisory for the affected versions of ClipBucket.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.5.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ClipBucket' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ClipBucket' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ClipBucketを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ClipBucket to 5.5.3ステージング環境で 5.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com