dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-47238

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 - #133, a normal authenticated user can edit another user's video subtitles because of a lack of authorization. They can upload subtitles, edit their name or delete them. This issue has been patched in version 5.5.3 - #133.

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 Insecure Direct Object Reference (IDOR) vulnerability where the application fails to verify ownership of video subtitles before allowing edit, upload, or delete operations. An authenticated user can access and modify any subtitle resource by manipulating identifiers in requests, as the backend does not validate that the requesting user owns the target subtitles.

MitigationUpgrade to ClipBucket version 5.5.3 - #133 which includes the authorization fix for subtitle access controls.

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
None
Integrity
Low
Availability
Low

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

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 ClipBucket installation and version
    Locate the ClipBucket installation directory on your web server. Check for a version file (often version.php, version.txt, or defined in config files) or inspect the main index.php and initialization files for a version constant. Compare the found version to 5.5.3.
    Affected if The installed version is ClipBucket v5 prior to 5.5.3
  2. Verify subtitles module is accessible
    Log into ClipBucket as an authenticated user and navigate to the video management section. Confirm that subtitle upload, edit, or delete functionality exists and is accessible to regular users (not just administrators).
    Affected if The subtitles feature is enabled and accessible to authenticated users
  3. Check for authorization validation in subtitle handlers
    Inspect the source code files responsible for subtitle operations (typically in functions, actions, or ajax directories). Look for code that validates user ownership before allowing edit, upload, or delete operations on subtitle records. Search for functions handling subtitle CRUD and examine their authorization logic.
    Affected if No ownership verification exists in the subtitle edit/upload/delete code paths, allowing any authenticated user to manipulate any subtitle by changing the identifier
  4. Test IDOR vulnerability manually (optional)
    Using two different authenticated user accounts, attempt to access or modify a subtitle belonging to user A while logged in as user B by manipulating the subtitle ID parameter in the request. Observe whether the operation succeeds without ownership validation.
    Affected if Requests with manipulated subtitle identifiers succeed without validating that the requesting user owns the target subtitle

You are affected if you run ClipBucket v5 versions before 5.5.3 with the subtitles feature enabled and the code lacks proper ownership validation for subtitle operations.

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 version 5.5.3 - #133 which includes the authorization fix for subtitle access controls.

Recommended fix High confidence

ClipBucket v5.5.3

  1. 1. Back up your current ClipBucket installation and database before upgrading.
  2. 2. Navigate to the official ClipBucket GitHub repository: https://github.com/ClipBucket/clipbucket
  3. 3. Download version 5.5.3 or the specific commit #133 that contains the security fix.
  4. 4. Extract the new version files and replace the existing installation files, or apply the specific patch from commit #133.
  5. 5. Verify that the fix has been applied by checking that subtitles belonging to other users can no longer be edited or deleted by an authenticated user without proper authorization.
  6. 6. Test the subtitle functionality to ensure legitimate users can still manage their own video subtitles.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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