# CVE-2025-64338: ClipBucket's Manage Photos Feature is Vulnerable to Stored XSS via Collection Name

> Authenticated users can inject scripts via photo collection names, leading to stored XSS and privilege escalation in the admin interface.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-93rh-fxxx-j38j

## What is CVE-2025-64338?

CVE-2025-64338 is a medium-severity cross-site scripting vulnerability in MacWarrior clipbucket-v5, published on 15 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ClipBucket v5 is an open source video sharing platform. In versions 5.5.2 - #156 and below, an authenticated regular user can create a photo collection whose Collection Name contains HTML/JavaScript payloads, which making ClipBucket’s Manage Photos feature vulnerable to Stored XSS. The payload is rendered unsafely in the Admin → Manage Photos interface, causing it to execute in the administrator’s browser, therefore allowing an attacker to target administrators and perform actions with elevated privileges. This issue is fixed in version 5.5.2 - #157.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Oxygenz Clipbucket.

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

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

## Is CVE-2025-64338 being exploited?

There is no known exploitation of CVE-2025-64338 in the wild and no public exploit code.

## 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-64338 and fix it if it is affected.

What it is: CVE-2025-64338 is a medium-severity cross-site scripting vulnerability in MacWarrior clipbucket-v5, published on 15 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-64338 in the wild and no public exploit code.

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-64338/ (Markdown: https://insights.sbomify.com/CVE-2025-64338/index.md)
```

## Sources

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

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