# CVE-2024-41713: Mitel MiCollab Path Traversal

> Unauthenticated attackers can exploit path traversal in Mitel MiCollab to view, corrupt, or delete user data and system configurations.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 7 Jan 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2024
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-8v9w-9wj4-52p3

## What is CVE-2024-41713?

CVE-2024-41713 is a critical path traversal vulnerability in n/a, published on 21 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could allow an unauthenticated attacker to conduct a path traversal attack, due to insufficient input validation. A successful exploit could allow unauthorized access, enabling the attacker to view, corrupt, or delete users' data and system configurations.

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

## Which versions are affected by CVE-2024-41713?

It affects 1 product.


Products: Mitel Micollab.

## How do I fix CVE-2024-41713?

No fix has been published for CVE-2024-41713 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Jan 2025.

## Is CVE-2024-41713 being exploited?

Yes. Attackers have exploited CVE-2024-41713 in the wild since at least 7 Jan 2025, including in ransomware campaigns.

Public exploit code:

- https://github.com/watchtowrlabs/Mitel-MiCollab-Auth-Bypass_CVE-2024-41713 (github_poc): https://github.com/watchtowrlabs/Mitel-MiCollab-Auth-Bypass_CVE-2024-41713
- Mitel MiCollab 企业协作平台 任意文件读取漏洞(CVE-2024-41713)由于Mitel MiCollab软件的 NuPoint 统一消息 (NPM) 组件中存在身份验证绕过漏洞，并且输入验证不足，未经身份验证的远程攻击者可利用该漏洞执行路径遍历攻击，成功利用可能导致未授权访问、破坏或删除用户的数据和系统配置。影响范围：version < MiCollab 9.8 SP2 (9.8.2.12) (github_poc): https://github.com/zxj-hub/CVE-2024-41713POC
- cve-2024-CVE-2024-41713 (github_poc): https://github.com/Sanandd/cve-2024-CVE-2024-41713
- A Python script to detect CVE-2024-41713, a directory traversal vulnerability in Apache HTTP Server, enabling unauthorized access to restricted resources. This tool is for educational purposes and authorized testing only. Unauthorized usage is unethical and illegal. (github_poc): https://github.com/amanverma-wsu/CVE-2024-41713-Scan
- Mitel MiCollab Authentication Bypass to Arbitrary File Read (github_poc): https://github.com/gunyakit/CVE-2024-41713-PoC-exploit
- Mitel MiCollab - Authentication Bypass (nuclei): http/cves/2024/CVE-2024-41713.yaml

## Other vulnerabilities in n/a

- [CVE-2022-26143](https://insights.sbomify.com/CVE-2022-26143/): MiCollab, MiVoice Business Express Access Control (critical 9.8, exploited in the wild)
- [CVE-2024-55550](https://insights.sbomify.com/CVE-2024-55550/): Mitel MiCollab Path Traversal (medium 4.4, exploited in the wild)
- [CVE-2024-35285](https://insights.sbomify.com/CVE-2024-35285/): Command injection in n/a (critical 9.8)
- [CVE-2024-35286](https://insights.sbomify.com/CVE-2024-35286/): SQL injection in n/a (critical 9.8)
- [CVE-2024-35314](https://insights.sbomify.com/CVE-2024-35314/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41713 and fix it if it is affected.

What it is: CVE-2024-41713 is a critical path traversal vulnerability in n/a, published on 21 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-41713 in the wild since at least 7 Jan 2025, including in ransomware campaigns.

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

## Sources

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

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