ClipBucket version 2.6 and earlier contains a critical vulnerability in the ofc_upload_image.php script located at /admin_area/charts/ofc-library/. This endpoint allows unauthenticated users to upload arbitrary files, including executable PHP scripts. Once uploaded, the attacker can access the file via a predictable path and trigger remote code execution.
Security readout for executives and security teams
Plain-English summary
ClipBucket 2.6 and earlier reportedly lets unauthenticated outsiders upload files that can execute server-side code. A successful attack could give control of the web application and host data. This is critical for any internet-facing ClipBucket deployment, but the supplied CVE data does not show CISA KEV listing or confirmed active exploitation.
Executive priority
Treat as urgent for any confirmed ClipBucket deployment. The vulnerability is remotely reachable, unauthenticated, and can lead to full application compromise. Prioritize asset discovery, containment of public exposure, and vendor-supported remediation before routine hardening work.
Technical view
The issue is CWE-434 in ofc_upload_image.php under the admin chart library. The bundle describes unauthenticated arbitrary upload of executable PHP, leading to remote code execution. CVSS v4.0 is 10.0 with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Highest exposure is public ClipBucket 2.6 or earlier, especially legacy video-sharing sites still reachable from the internet. The supplied affected record is inconsistent, listing version "0" while the description says 2.6 and earlier, so asset confirmation matters.
Exploitation context
Public exploit references exist from Rapid7 Metasploit and Packet Storm, so the technique is publicly documented. However, the source bundle marks KEV as false and provides no cited evidence of active exploitation in the wild.
Researcher notes
Evidence supports critical severity and public exploit availability, but not confirmed active exploitation. The affected-version metadata conflicts with the narrative description, so validation should rely on local version evidence and vendor or CVE updates rather than assumptions.
Mitigation direction
Identify and prioritize all ClipBucket deployments, especially internet-facing legacy instances.
Check official ClipBucket and CVE guidance for supported fixed versions or vendor mitigations.
Restrict public access to administrative and upload-related paths where business permits.
Remove unsupported ClipBucket instances or isolate them behind strong access controls.
Review uploaded files and webroot contents for unexpected executable files.
Validation and detection
Confirm product name, installed version, and exposure path for every ClipBucket instance.
Review web server logs for unexpected upload activity and suspicious PHP file access.
Inspect application upload directories and webroot for unauthorized executable files.
Verify administrative and upload endpoints are not anonymously reachable from the internet.
Track CVE, VulnCheck, and vendor pages for updated affected-version and remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.