/

CVE-2026-80138

Severity:

CRITICAL RISK

(9.8)

OS Command Injection (CWE-78) in ClipBucket V5 Installer

CVE-2026-80138

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-78

Impact:

Unauthenticated Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

ClipBucket V5's web installer does not adequately validate or escape the php_cli_filepath parameter before using it in a shell command. An unauthenticated attacker may submit a crafted POST request to execute arbitrary commands with the privileges of the web server process.

Affected context

The vulnerability occurs in the ClipBucket V5 web installer when the php_cli_filepath parameter is incorporated into shell execution without sufficient input validation or escaping. Risk is greatest when the installer endpoint remains accessible and accepts attacker-controlled POST data before deployment is completed or access is restricted.

Exploit preconditions

  • Attack surface: ClipBucket V5 web installer HTTP endpoint
  • Required access: No authentication may be required when the installer is exposed
  • Trigger point: Processing a POST request containing the php_cli_filepath parameter
  • Why exploitation is possible: The parameter reaches shell execution without reliably constraining or neutralizing shell metacharacters and command syntax

Why this happens

The underlying flaw is an OS command injection caused by passing attacker-controlled input into a shell command without using a safe execution pattern. This behavior maps to CWE-78: Improper Neutralization of Special Elements used in an OS Command, because input intended to identify a PHP CLI executable can instead influence command interpretation.

Potential impact

  • An attacker may execute arbitrary operating-system commands
  • The web server account could be compromised
  • Application files, credentials, or stored data may be accessed or modified
  • The host could be used for persistence, lateral movement, or further attacks
  • Application availability and data integrity may be affected

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from installer operations and reducing trust in request parameters.

Common defensive patterns include:

  • Invoke the PHP executable through a process API that passes arguments separately rather than through a shell
  • Allow only explicitly configured executable paths or tightly constrained identifiers
  • Apply strict server-side validation before any process invocation
  • Keep the web installer inaccessible after setup and restrict administrative installation paths
  • Run the web server with the minimum filesystem and process privileges required
  • Use deployment controls that prevent untrusted users from reaching installation endpoints

How teams detect issues like this

Organizations can look for:

  • Static analysis findings where request parameters flow into shell execution, subprocess calls, or command-building functions
  • Code review signals such as string concatenation or interpolation in process commands
  • Installer routes that accept executable paths or command fragments from HTTP input
  • Web application logs containing unusual installer POST requests or repeated attempts to alter execution parameters
  • Policy checks that prohibit shell-based process invocation for user-controlled values

Automated application-security and code-review tools may help identify these data-flow patterns.

Sources

SourceLink
github.comgithub.com/MacWarrior/clipbucket-v5
github.comgithub.com/MacWarrior/clipbucket-v5/blob/5.5.3-%23153/upload/cb_install/functions_install.php
github.comgithub.com/MacWarrior/clipbucket-v5/blob/5.5.3-%23153/upload/includes/classes/system.class.php
github.comgithub.com/MacWarrior/clipbucket-v5/commit/36e7c6cfd81f62a091d2aeef96a8fc2fc2d85dc4
vulncheck.comvulncheck.com/advisories/clipbucket-v5-5.5.1-through-5.5.3-153-os-command-injection-via-installer-php-cli-filepath-parameter

Frequently asked

questions

Yes. When the ClipBucket web installer is exposed and does not require authentication, an attacker may submit a crafted HTTP POST request remotely.

The described issue does not require authentication. The key condition is access to the vulnerable installer endpoint.

Avoid passing request-controlled data through a shell. Use a safe process-execution interface with a fixed executable and separately validated arguments.

Restrict installer exposure, enforce strict allowlist validation, review all user-input-to-process execution flows, and run the web server with least privilege.

Find out what's already
exploitable in your codebase.