CVE-2026-45060
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 · uneditedClipBucket v5 is an open source video sharing platform. Prior to version 5.5.3 - #129, the actions/progress_video.php endpoint is vulnerable to blind SQL injection. Any unauthenticated user can exploit the ids parameter to execute SQL queries and exfiltrate sensitive data. This issue has been patched in version 5.5.3 - #129.
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 confidenceBlind SQL injection vulnerability in ClipBucket v5's actions/progress_video.php endpoint. The 'ids' parameter accepts unsanitized user input that is directly used in SQL queries, allowing any unauthenticated attacker to execute arbitrary SQL commands and exfiltrate sensitive data from the database.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate ClipBucket installation and determine versionCheck for ClipBucket by looking for the main index.php or config.php file in the web root. Open version.php or check the admin dashboard for the installed version number.Affected if The installed version is ClipBucket v5 and has not been patched to v5.5.3 or later.
-
Verify the vulnerable file existsCheck if the file actions/progress_video.php exists in the web application directory.Affected if The file exists and is accessible via the web server.
-
Confirm the ids parameter is exposedInspect the progress_video.php file and check if the ids parameter is used in database queries without proper sanitization or parameterized queries.Affected if The code uses the ids parameter directly in SQL queries without input validation or prepared statements.
-
Test unauthenticated access to the endpointSend a request to actions/progress_video.php without authentication credentials, including a test value in the ids parameter.Affected if The endpoint accepts requests without requiring authentication.
The environment is affected if ClipBucket v5 is installed with the actions/progress_video.php file accessible and the ids parameter accepts unauthenticated input without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to ClipBucket v5.5.3 - #129 or later, which contains the patch addressing the SQL injection vulnerability in the ids parameter.
ClipBucket v5.5.3 - #129
- Upgrade ClipBucket to version 5.5.3 or later (specifically version 5.5.3 including commit #129)
- Verify that the upgrade was successful by checking the actions/progress_video.php endpoint is no longer vulnerable
- Test that the ids parameter is properly sanitized and no longer accepts SQL injection payloads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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