CVE-2026-42846
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 - #140, ClipBucket's Remote Play feature allows any authenticated user to add a video by importing an external URL as the source. Some shell commands are run with the URL as a parameter. The URL is concatenated directly into shell commands without escaping then executed, so any shell metacharacter in the URL is interpreted. This results in arbitrary command execution. This issue has been patched in version 5.5.3 - #140.
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 confidenceCommand injection vulnerability in ClipBucket v5's Remote Play feature allows authenticated users to execute arbitrary commands by providing specially crafted URLs. The URL parameter is concatenated directly into shell commands without escaping, allowing shell metacharacters to break out of the intended command context.
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.
-
Identify ClipBucket installation and versionLocate the ClipBucket installation directory and check the version file (typically version.php, config.php, or similar). Common paths include /var/www/html/clipbucket/ or the web root if installed there.Affected if The installed version is ClipBucket v5.x (any version prior to 5.5.3, as 5.5.3 and later contain the fix)
-
Verify Remote Play feature is enabledSearch the ClipBucket admin panel or configuration files for the Remote Play setting. Look for options like 'remote_play', 'remote_play_enabled', or similar in the database or config files.Affected if The Remote Play feature is enabled (set to true, 1, or 'yes') in the configuration
-
Confirm authenticated user access existsReview user account configurations to determine if any non-admin or lower-privilege authenticated users exist in the system. Check user tables or admin panel user management.Affected if There are authenticated users with access to the Remote Play feature (any user account beyond a clean install indicates potential attack surface)
-
Inspect Remote Play URL handling codeLocate the Remote Play functionality code (typically in includes/functions or similar directories). Search for the URL parameter handling in files related to remote play, streaming, or media playback.Affected if The code directly passes the URL parameter to shell execution functions (exec, shell_exec, system, passthru) without sanitization or escaping
A user is affected if they run ClipBucket v5.x prior to 5.5.3 with the Remote Play feature enabled and accessible to authenticated users, as the vulnerable URL parameter handling can be exploited for command injection.
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 - #140 immediately. Until patched, disable the Remote Play feature for all users and restrict authenticated access to minimize attack surface.
5.5.3 - #140
- Backup the ClipBucket installation and database before upgrading
- Download ClipBucket version 5.5.3 - #140 from the official repository or source
- Replace the existing ClipBucket files with the new version
- Verify the Remote Play feature now properly sanitizes URL inputs before use
- Test that authenticated users can still add videos via external URLs without command injection
- Ensure no regressions in other functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42846 — 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-42846 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