dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-45418

HIGH · 8.8 CVSS v3.1 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 version 5.5.3 - #132, any authenticated user who can upload videos can add multiple subtitles from different files and change their title (English, Spanish...). The POST /actions/subtitle_edit.php request used to change their title includes a number parameter which is vulnerable to SQL Injection. A boolean-based blind SQL injection can be used to exfiltrate sensitive data. This issue has been patched in version 5.5.3 - #132.

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

ClipBucket v5 prior to version 5.5.3 contains an authenticated blind SQL injection in the POST /actions/subtitle_edit.php endpoint. The 'number' parameter used when changing subtitle titles is not properly sanitized, allowing any authenticated user with video upload privileges to exfiltrate sensitive data from the database via boolean-based blind SQLi.

MitigationUpgrade to ClipBucket v5.5.3 or later (patch #132) which addresses the SQL injection vulnerability. As a temporary measure, restrict video upload permissions to trusted users only until the patch can be applied.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed ClipBucket version
    Locate the version number in the ClipBucket installation - check the admin dashboard version display, a version.php file in the root directory, or the database version记录
    Affected if The installed version is 5.x prior to version 5.5.3 (any 5.0 through 5.5.2 is affected)
  2. Verify vulnerable endpoint exists
    Confirm the file /actions/subtitle_edit.php exists in the web accessible directory
    Affected if The file exists and responds to POST requests
  3. Review user accounts with video upload access
    Check user accounts and their group permissions in the ClipBucket admin panel or database - look for users assigned to groups with video upload or subtitle editing privileges
    Affected if There are user accounts with video upload privileges that are not fully trusted or are accessible to untrusted personnel
  4. Test parameter handling in subtitle_edit.php
    Submit a POST request to /actions/subtitle_edit.php with a test value in the 'number' parameter and observe if it is processed without sanitization or triggers SQL errors
    Affected if The 'number' parameter accepts raw input and the application does not sanitize or parameterize the value before using it in a database query

You are affected if your ClipBucket installation is version 5.0 through 5.5.2, the subtitle_edit.php endpoint exists, and you have any authenticated user with video upload privileges that could access the vulnerable parameter.

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 or later (patch #132) which addresses the SQL injection vulnerability. As a temporary measure, restrict video upload permissions to trusted users only until the patch can be applied.

Recommended fix High confidence

ClipBucket v5.5.3

  1. 1. Backup your current ClipBucket installation and database before upgrading.
  2. 2. Download ClipBucket version 5.5.3 or later from the official repository (github.com).
  3. 3. Replace the existing files with the new version, preserving your configuration and upload directories.
  4. 4. Verify that /actions/subtitle_edit.php has been updated with parameterized queries to prevent SQL injection.
  5. 5. Test the subtitle editing functionality to confirm the fix works correctly.
  6. 6. Ensure that only trusted users have subtitle upload/edit permissions as a defense-in-depth measure.
Caveat Review release notes for any configuration changes or database schema updates between your current version and 5.5.3

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45418 — 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-45418 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