CVE-2025-67886 describes a code execution condition in Bitrix24 through 25.100.300. According to the provided description, an actor who already has SOURCE/WRITE permissions for the Translate Module can upload a PHP file together with a .htaccess file and then execute the uploaded code. The issue is therefore tied to the application's handling of uploaded files in the Translate Module, where executable server-side content can be placed in a web-accessible location and invoked. The supplier disputes the issue as a vulnerability, stating that this behavior is intended for highly privileged users who are allowed to upload new translated pages to the website.
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 (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2025-67886, a remote code execution vulnerability in Bitrix24 (Translate Module) versions <= 25.100.300. The main file, CVE-2025-67886.php, is a PHP script that automates the exploitation process. It requires the attacker to provide the target URL, a valid username, and password. The script logs into the Bitrix24 instance, retrieves a CSRF token, uploads a malicious tar.gz archive containing a PHP web shell, and triggers its extraction and application via specific AJAX endpoints. Once the shell is deployed, the script provides an interactive command shell to the attacker by sending commands via custom HTTP headers to the uploaded shell.php file. The exploit demonstrates a full attack chain from authentication bypass to remote code execution. The repository also includes a brief README describing the vulnerability.
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.
2 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.