Clip Bucket 5.5.2 file_downloader.php File command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Clip Bucket 5.5.2. The impacted element is an unknown function of the file file_downloader.php. The manipulation of the argument File results in Remote Privilege Escalation. This vulnerability is identified as CVE-2025-55911. The attack can be executed remotely. Additionally, an exploit exists.
Details
A vulnerability classified as critical has been found in Clip Bucket 5.5.2. Affected is an unknown part of the file file_downloader.php. The manipulation of the argument file with an unknown input leads to a remote privilege escalation vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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
The advisory is shared for download at medium.com. This vulnerability is traded as CVE-2025-55911 since 08/16/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1202.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:file_downloader.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (52434) and EUVD (EUVD-2025-29929). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/16/2025 CVE reserved09/18/2025 Advisory disclosed
09/18/2025 VulDB entry created
09/26/2025 VulDB entry last update
Sources
Advisory: medium.comStatus: Not defined
CVE: CVE-2025-55911 (🔒)
GCVE (CVE): GCVE-0-2025-55911
GCVE (VulDB): GCVE-100-324936
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/18/2025 19:22Updated: 09/26/2025 00:29
Changes: 09/18/2025 19:22 (51), 09/18/2025 22:00 (13), 09/19/2025 00:08 (2), 09/26/2025 00:29 (2)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.