# CVE-2025-55912: File upload in n/a

> Unauthenticated attackers can upload arbitrary files via the plupload endpoint in ClipBucket, potentially leading to remote code execution.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-v9w7-v37j-9778

## What is CVE-2025-55912?

CVE-2025-55912 is a high-severity vulnerability in n/a, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in ClipBucket 5.5.0 and prior versions allows an unauthenticated attacker can exploit the plupload endpoint in photo_uploader.php to upload arbitrary files without any authentication, due to missing access controls in the upload handler

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Oxygenz Clipbucket.

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

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

## Is CVE-2025-55912 being exploited?

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

Public exploit code:

- ClipBucket 5.5.0 - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [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-55912 and fix it if it is affected.

What it is: CVE-2025-55912 is a high-severity vulnerability in n/a, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55912 in the wild and no public exploit code.

Affected product: n/a. 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-55912/ (Markdown: https://insights.sbomify.com/CVE-2025-55912/index.md)
```

## Sources

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

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