CVE-2025-67886
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBitrix24 through 25.100.300 allows Remote Code Execution because an actor with SOURCE/WRITE permissions for the Translate Module can upload and execute code by sending a PHP file and a .htaccess file. NOTE: this is disputed by the Supplier because this is intended behavior for the high-privileged users who can upload new translated pages to the website.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBitrix24's Translate Module allows users with SOURCE/WRITE permissions to upload files including PHP scripts and .htaccess configurations. This enables Remote Code Execution by uploading executable PHP files that can then be accessed via the web server. The vulnerability stems from insufficient validation of uploaded file types in the translation upload functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Bitrix24 installation presenceSearch for Bitrix24 core files or directories (e.g., index.php with Bitrix signatures, /bitrix/ directory, or configuration files containing 'bitrix24' in web root)Affected if Bitrix24 is installed in the environment
-
Verify Translate Module is installed and activeCheck for the presence of the translation module component in the Bitrix24 module directory or administrative interfaceAffected if The Translate Module is present and enabled in Bitrix24
-
Identify users with SOURCE/WRITE permissionsReview user roles and permissions within the Translate Module administrative panel to locate accounts with SOURCE or WRITE access levelsAffected if Any user account has SOURCE or WRITE permissions in the Translate Module
-
Test file upload functionality in Translate ModuleUsing an account with SOURCE/WRITE permissions, attempt to upload a test file through the translation upload feature to verify the endpoint accepts filesAffected if The file upload functionality in the Translate Module is accessible and accepts file uploads
-
Verify uploaded files are served from web-accessible locationCheck the storage path of uploaded translation files to determine if they are placed within the web document root and accessible via HTTPAffected if Uploaded translation files are stored in a web-accessible directory and can be retrieved via the web server
A user is affected if Bitrix24 with the Translate Module is installed, the module accepts file uploads from users with SOURCE/WRITE permissions, and uploaded files are served from a web-accessible location allowing PHP execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict or blacklist PHP file uploads in the Translate Module, store uploaded files outside the web root or with execute permissions disabled, and implement strict file type validation. Alternatively, refactor the translation storage mechanism to use non-PHP formats.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data