Code InjectionWeakness · CWE-94

CVE-2025-67887

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
1C-Bitrix through 25.100.500 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 confidence

1C-Bitrix through version 25.100.500 contains an RCE vulnerability in the Translate Module where users with SOURCE/WRITE permissions can upload PHP files along with .htaccess files, enabling execution of arbitrary code on the server.

MitigationRestrict or disable PHP file uploads in the Translate Module for untrusted high-privileged users, or implement strict allowlist controls on permitted file types; consider upgrading if vendor releases a patch.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the system is running 1C-Bitrix
    Check for 1C-Bitrix signatures in the web application directory, such as the presence of bitrix directory structure, /bitrix/admin/ login pages, or bitrix framework files in the web root.
    Affected if The system is confirmed to be a 1C-Bitrix installation.
  2. Determine the installed 1C-Bitrix version
    Access the administrative panel and navigate to System Settings > Product Information, or locate the version file in the bitrix directory (typically /bitrix/modules/main/include/version.php) and read the version constants.
    Affected if The installed version is 25.100.500 or any earlier version (any version through 25.100.500 is affected).
  3. Verify if the Translate Module is installed and active
    Log into the administrative panel and check Module Settings > Module List, or examine the /bitrix/modules/ directory for the presence of the translate module folder.
    Affected if The Translate Module is installed and enabled on the system.
  4. Check for users with SOURCE/WRITE permissions on the Translate Module
    In the administrative panel, navigate to User permissions or Access Rights settings, and review which users or user groups have SOURCE or WRITE level permissions assigned to the Translate Module.
    Affected if Any user account has SOURCE or WRITE permissions assigned to the Translate Module.
  5. Inspect upload configuration for the Translate Module
    Access the Translate Module settings panel and review the file upload or file type restrictions configuration. Look for settings that control allowed file extensions during translation file uploads.
    Affected if PHP file extensions are permitted or not explicitly blocked in the upload settings, allowing both PHP and .htaccess files to be uploaded.

The system is affected if it is running 1C-Bitrix version 25.100.500 or earlier, has the Translate Module enabled, and permits users with SOURCE/WRITE permissions to upload PHP files along with .htaccess files through the module.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable PHP file uploads in the Translate Module for untrusted high-privileged users, or implement strict allowlist controls on permitted file types; consider upgrading if vendor releases a patch.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67887 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67887 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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