Loading vulnerability…
CVE-2025-67887 describes a code execution condition in 1C-Bitrix through 25.100.500. According to the provided description, an actor with SOURCE/WRITE permissions in 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 within the Translate Module, where a privileged user can cause server-side executable content to be placed in a web-accessible location and interpreted by the web server. The supplier disputes the classification as a vulnerability, stating that this behavior is intended for highly privileged users who are allowed to upload 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-67887, a remote code execution vulnerability in the 1C-Bitrix Translate Module (versions <= 25.100.500). The main file, CVE-2025-67887.php, is a PHP script that automates the exploitation process. It requires the attacker to provide the target URL and valid Bitrix credentials. The script logs into the Bitrix instance, uploads a malicious archive containing a PHP web shell, extracts and applies the archive via specific AJAX endpoints, and then provides an interactive shell for remote command execution. The exploit leverages several Bitrix AJAX endpoints to achieve code execution. The repository is structured simply, with the exploit script and a brief README. The exploit is operational, providing a working shell if the target is vulnerable and credentials are valid.
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.