# CVE-2026-80138: ClipBucket V5 5.5.1 through 5.5.3-#153 OS Command Injection via Installer php_cli_filepath Parameter

> Unauthenticated attackers can execute arbitrary commands via the installer's php_cli_filepath parameter in ClipBucket V5.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-h7wf-mrfw-7fxq

## What is CVE-2026-80138?

CVE-2026-80138 is a critical command injection vulnerability in MacWarrior clipbucket-v5, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ClipBucket V5's web installer fails to properly validate or escape the php_cli_filepath parameter before passing it to shell execution. Unauthenticated attackers can submit a crafted POST request to the installer with a malicious php_cli_filepath value to execute arbitrary commands as the web server user.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-80138 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80138 is a critical command injection vulnerability in MacWarrior clipbucket-v5, published on 25 Aug 2026. 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-2026-80138 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-80138/ (Markdown: https://insights.sbomify.com/CVE-2026-80138/index.md)
```

## Sources

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

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