# CVE-2025-67887: Code injection in n/a

> High-privileged users can upload and execute PHP code via the Translate Module, enabling remote code execution on the web application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-2636-hvcv-37w8

## What is CVE-2025-67887?

CVE-2025-67887 is a critical code injection vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-67887?


## How do I fix CVE-2025-67887?

No fix has been published for CVE-2025-67887 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-67887 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67887 exists.

Public exploit code:

- 1C-Bitrix <= 25.100.500 (Translate Module) Remote Code Execution Vulnerability (github_poc): https://github.com/reewardius/CVE-2025-67887
- https://github.com/cyberok-org/CVE-2025-67887 (github_poc): https://github.com/cyberok-org/CVE-2025-67887

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67887 and fix it if it is affected.

What it is: CVE-2025-67887 is a critical code injection vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67887 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67887/ (Markdown: https://insights.sbomify.com/CVE-2025-67887/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67887
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67887
- OSV: https://osv.dev/vulnerability/CVE-2025-67887

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67887/
Summaries are generated and may contain mistakes; the official description above is the record.