Skip to main content
VulnerabilityPublished

CVE-2025-55911: Command Injection

Source CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 18 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 33 days before disclosure

  2. First Exploit-DB entry (opens in a new tab)

    ClipBucket 5.5.2 Build #90 - Server-Side Request Forgery (SSRF)

    , 2 days before disclosure

  3. CVE published

    on cve.org

    , t = 0

  4. In Threat Radar

    record ingested

    , the same day as disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate mitigation should involve restricting access to the file_downloader.php script via network controls such as firewall rules or web application firewalls (WAF) to limit exposure to untrusted sources.
  2. Organizations should monitor web server logs for suspicious requests targeting the 'file' parameter to detect potential exploitation attempts.
  3. If possible, disable or remove the file_downloader.php functionality temporarily until a patch or official fix is released.
  4. Implement strict input validation and sanitization on all user-controllable parameters, especially those involving file handling.
  5. Conduct a thorough security review and penetration test of the Clip Bucket deployment to identify other potential vulnerabilities.
  6. Stay informed on vendor updates or community advisories for Clip Bucket to apply patches promptly once available.
  7. Employ network segmentation to isolate media servers from critical infrastructure to limit the blast radius of a compromise.

Description

An issue Clip Bucket v.5.5.2 Build#90 allows a remote attacker to execute arbitrary codes via the file_downloader.php and the file parameter

References

Community reviews

Loading reviews…