Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-80138 – Unauthenticated OS Command Injection (RCE) – ClipBucket V5 5.5.1 through 5.5.3-#153

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-80138 is an OS command injection vulnerability (CWE-78) in the web installer of ClipBucket V5, a video-sharing platform. The php_cli_filepath parameter of the installer is not properly validated or escaped before being passed to shell execution, allowing an unauthenticated remote attacker to execute arbitrary commands as the web server user. The flaw carries a critical CVSS score of 9.2.

Technical details

  • Root cause: the installer fails to validate or escape the php_cli_filepath parameter before passing it to a shell execution call.
  • Trigger condition: an attacker sends a crafted POST request to the ClipBucket web installer supplying a malicious value for php_cli_filepath.
  • Attack vector: network-based, requires no authentication and no user interaction.
  • Impact: arbitrary OS command execution in the context of the web server process, leading to full compromise of confidentiality, integrity, and availability of the affected host.

Affected software

  • ClipBucket V5, versions 5.5.1 through 5.5.3-#153

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical) — 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

Mitigation and recommended actions

  • Immediate: upgrade to a fixed ClipBucket V5 build that includes the patch addressing the php_cli_filepath validation issue (fix committed to the official repository after version 5.5.3-#153).
  • If a patch cannot be applied immediately: restrict or disable access to the web installer (e.g., remove or block the installer path after initial setup, restrict it to trusted IPs), and ensure installer endpoints are not exposed on internet-facing systems.
  • General hardening: run the web server process with least-privilege permissions to limit the impact of any command execution, and monitor for unexpected outbound connections or process spawning from the web server user.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: ClipBucketV5, maintained by Oxygenz

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge