# CVE-2015-8358: Path traversal in n/a

> Remote administrators can execute arbitrary local files via path traversal in the Bitrix mpbuilder module.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5vgp-64gj-j392

## What is CVE-2015-8358?

CVE-2015-8358 is a critical path traversal vulnerability in n/a, published on 16 Dec 2015. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Directory traversal vulnerability in the bitrix.mpbuilder module before 1.0.12 for Bitrix allows remote administrators to include and execute arbitrary local files via a .. (dot dot) in the element name of the "work" array parameter to admin/bitrix.mpbuilder_step2.php.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2015-8358?

It affects 1 product.


Products: Bitrix Mpbuilder.

## How do I fix CVE-2015-8358?

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

## Is CVE-2015-8358 being exploited?

There is no known exploitation of CVE-2015-8358 in the wild and no public exploit code.

Public exploit code:

- Bitrix bitrix.mpbuilder Module 1.0.10 - Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8358 and fix it if it is affected.

What it is: CVE-2015-8358 is a critical path traversal vulnerability in n/a, published on 16 Dec 2015. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8358 in the wild and no public exploit code.

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-2015-8358/ (Markdown: https://insights.sbomify.com/CVE-2015-8358/index.md)
```

## Sources

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

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