dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42847

HIGH · 7.1 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL Injection vulnerability in ClipBucket v5 admin_area/action_logs.php where the $_GET['type'] parameter is directly concatenated into a SQL WHERE clause without parameterization in the fetch_action_logs() function, allowing authenticated administrators to inject malicious SQL via UNION-based attacks and exfiltrate sensitive database content.

MitigationUpgrade to ClipBucket v5.5.3 - #122 or later which includes parameterized queries. If immediate upgrade is not possible, implement input validation and replace direct SQL concatenation with prepared statements for the action_type field.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ClipBucket v5 installation
    Check for ClipBucket installation by looking for the main index.php or config.php file in the web root. Look for version information in version.php, about.php, or similar files typically found in the application root or includes directory.
    Affected if ClipBucket v5 is installed (any v5 version prior to v5.5.3 build #122)
  2. Locate the vulnerable action_logs.php file
    Check for the presence of admin_area/action_logs.php in the web root directory. This file should exist in the administrative interface path.
    Affected if The file admin_area/action_logs.php exists in the ClipBucket installation
  3. Identify the fetch_action_logs function and SQL handling
    Open admin_area/action_logs.php and search for the fetch_action_logs() function. Examine how the $_GET['type'] parameter is used within SQL queries - look for direct concatenation in WHERE clauses without parameterization or escaping.
    Affected if The fetch_action_logs() function uses $_GET['type'] directly in SQL queries without prepared statements, binding, or proper escaping
  4. Confirm admin access is required
    Verify that the vulnerability requires authenticated administrator access to the admin_area. Check if action_logs.php includes authentication checks before processing the type parameter.
    Affected if The page is accessible to authenticated administrators and the type parameter is processed without additional sanitization beyond authentication

A user is affected if they run any version of ClipBucket v5 prior to v5.5.3 build #122 where the admin_area/action_logs.php file exists and the $_GET['type'] parameter is directly concatenated into SQL queries in the fetch_action_logs() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ClipBucket v5.5.3 - #122 or later which includes parameterized queries. If immediate upgrade is not possible, implement input validation and replace direct SQL concatenation with prepared statements for the action_type field.

Recommended fix High confidence

ClipBucket v5.5.3

  1. Backup the existing ClipBucket installation and its database before proceeding with any changes
  2. Download ClipBucket v5.5.3 (commit #122 or later) from the official GitHub repository at github.com
  3. Replace the existing ClipBucket files with the new version 5.5.3 files, preserving any custom configurations
  4. Run any database migration scripts included in the 5.5.3 release if applicable
  5. Verify the fix by confirming that the 'type' parameter in admin_area/action_logs.php is now properly parameterized and no longer directly concatenated into SQL queries
  6. Test the admin_area/action_logs.php endpoint with various 'type' parameter values to ensure functionality works correctly and the SQL injection vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42847 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data