ClipBucket versions prior to 4.0.0 Release 4902 are vulnerable to arbitrary file upload via the 'name' parameter in actions/beats_uploader.php or actions/photo_uploader.php, and via the 'coverPhoto' parameter in edit_account.php. The application fails to properly validate or sanitize uploaded files, allowing attackers to upload malicious files to the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/multi/http/clipbucket_fileupload_exec.rb) that exploits an unauthenticated arbitrary file upload vulnerability in ClipBucket versions before 4.0.0 (Release 4902), tracked as CVE-2018-7665. The exploit works by uploading a malicious PHP payload (such as a Meterpreter reverse shell) to the vulnerable /actions/beats_uploader.php endpoint without authentication. After uploading, the module executes the payload, granting the attacker remote code execution on the target server. The module includes a check method to verify the presence of ClipBucket and the vulnerable endpoint. The exploit is weaponized, as it is part of the Metasploit framework and allows for customizable payloads. The only file in the repository is a Ruby script implementing the exploit logic.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.