# CVE-2025-21623: ClipBucket V5 Unauthenticated Template Directory Update to Denial-of-Service

> Unauthenticated attackers can exploit a path traversal vulnerability in ClipBucket V5 to change the template directory, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2025
- **Updated:** 7 Jan 2025
- **Also known as:** GHSA-ffhj-hprx-7qvr

## What is CVE-2025-21623?

CVE-2025-21623 is a high-severity path traversal vulnerability in MacWarrior clipbucket-v5, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ClipBucket V5 provides open source video hosting with PHP. Prior to 5.5.1 - 238, ClipBucket V5 allows unauthenticated attackers to change the template directory via a directory traversal, which results in a denial of service.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-21623?

It affects 1 product.


Products: Oxygenz Clipbucket.

## How do I fix CVE-2025-21623?

No fix has been published for CVE-2025-21623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-21623 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-21623 exists.

## Other vulnerabilities in MacWarrior clipbucket-v5

- [CVE-2026-21875](https://insights.sbomify.com/CVE-2026-21875/): ClipBucket v5 Vulnerable to Blind SQL Injection through Channel Comments (critical 9.8)
- [CVE-2025-67418](https://insights.sbomify.com/CVE-2025-67418/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-21624](https://insights.sbomify.com/CVE-2025-21624/): ClipBucket V5 Playlist Cover File Upload to Remote Code Execution (critical 9.8)
- [CVE-2024-54135](https://insights.sbomify.com/CVE-2024-54135/): Untrusted Deserialization in ClipBucket-v5 Version 2.0 to 5.5.1 Revision 199 (critical 9.8)
- [CVE-2024-54136](https://insights.sbomify.com/CVE-2024-54136/): Untrusted Deserialization in ClipBucket-v5 Version 5.5.1 Revision 199 and Below (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-21623 and fix it if it is affected.

What it is: CVE-2025-21623 is a high-severity path traversal vulnerability in MacWarrior clipbucket-v5, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-21623 exists.

Affected product: MacWarrior clipbucket-v5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-21623/ (Markdown: https://insights.sbomify.com/CVE-2025-21623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-21623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-21623
- OSV: https://osv.dev/vulnerability/CVE-2025-21623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-21623/
Summaries are generated and may contain mistakes; the official description above is the record.