# CVE-2026-77928: ClipBucket < 5.5.3-#182 Blind SQL Injection via Private Message Deletion Endpoint

> Authenticated attackers can extract database contents, including credentials, via blind SQL injection in the private message deletion endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-wwv3-r4qp-89fg

## What is CVE-2026-77928?

CVE-2026-77928 is a high-severity SQL injection vulnerability in MacWarrior clipbucket-v5, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ClipBucket v5 before 5.5.3-#182 contains a blind SQL injection vulnerability that allows authenticated users to extract arbitrary database contents by submitting the msg_id parameter as an array to bypass the clean_requests() sanitization function in ClipBucket.class.php. Attackers can pass unsanitized array elements through the deletion handler in private_message.php into cb_pm::delete_msg(), which interpolates the unescaped message ID directly into a SQL query string, enabling time-based blind SQL injection to retrieve all user credential hashes and email addresses.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-77928?


## How do I fix CVE-2026-77928?

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

## Is CVE-2026-77928 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77928 and fix it if it is affected.

What it is: CVE-2026-77928 is a high-severity SQL injection vulnerability in MacWarrior clipbucket-v5, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77928 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-2026-77928/ (Markdown: https://insights.sbomify.com/CVE-2026-77928/index.md)
```

## Sources

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

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