CVE-2013-10040 affects ClipBucket 2.6 and earlier. The vulnerability is in the /admin_area/charts/ofc-library/ofc_upload_image.php script, which permits unauthenticated users to upload arbitrary files. Because the upload mechanism does not adequately restrict file type or executable content, an attacker can upload a PHP script and then request it from a predictable web-accessible location. This results in remote code execution on the server in the security context of the web application.
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 (clipbucket_upload_exec.rb) that exploits an unauthenticated file upload vulnerability in ClipBucket version 2.6 and below (CVE-2013-10040). The exploit targets the /admin_area/charts/ofc-library/ofc_upload_image.php script, which allows arbitrary PHP code to be uploaded and executed without authentication. The module uploads a PHP payload (provided by Metasploit) and then accesses it via the web server to achieve remote code execution. The code is written in Ruby and follows the standard Metasploit module structure, utilizing the HttpClient and FileDropper mixins. The exploit is operational and provides remote code execution as the web server user if the target is vulnerable.
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.
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.