CVE-2025-34100 is an unrestricted file upload vulnerability in BuilderEngine 3.5.0 arising from its integration of the elFinder 2.0 file manager and the jQuery File Upload plugin. According to the provided content, the upload functionality does not properly validate or restrict uploaded file types or upload destinations. As a result, an unauthenticated attacker can upload a malicious PHP file through the exposed file manager functionality and then access that file to execute arbitrary PHP code on the server. Although the underlying weakness is attributed to the jQuery File Upload component, BuilderEngine’s insecure integration and lack of access controls make the vulnerable upload path reachable by unauthenticated users, leading to remote code execution in the context of the web server process.
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 (2 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/http/builderengine_upload_exec.rb) targeting BuilderEngine 3.5.0. The exploit abuses an arbitrary file upload vulnerability in the elFinder 2.0 jquery-file-upload plugin, allowing an attacker to upload and execute a PHP payload on the target server. The module first checks for the presence of the vulnerable upload endpoint, then crafts and uploads a PHP payload using a multipart/form-data POST request. If the upload is successful, the module triggers the payload by sending a GET request to the uploaded file, resulting in remote code execution. The exploit is weaponized, supporting customizable Metasploit PHP payloads, and is associated with CVE-2025-34100. The only file in the repository is a Ruby script compatible with the Metasploit framework.
4 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.