CVE-2024-41713
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Yes. Path traversal sends `../` sequences in the request, which WAF rules catch, including the common encodings. Cloudflare also publishes a rule written for this CVE.
Cloudflare · 1 rule (Block) · since 6 Jan 2025
- Mitel MiCollab - Auth Bypass - CVE:CVE-2024-41713 · Cloudflare Specials
Also consider: canonical path validation
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-41713 being exploited?
Yes. CVE-2024-41713 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-41713?
CVE-2024-41713 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-41713?
Yes. A fix has been recorded for CVE-2024-41713. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-41713 affect?
CVE-2024-41713 affects mitel:micollab. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
public exploits
Unvetted proof-of-concept code on GitHub: 5 GitHub proofs of concept · 1 Nuclei template
- Mitel MiCollab - Authentication Bypass · detection template · high
- watchtowrlabs/Mitel-MiCollab-Auth-Bypass_CVE-2024-41713 · 20 ★
- zxj-hub/CVE-2024-41713POC · 0 ★
- Sanandd/cve-2024-CVE-2024-41713 · 0 ★
- amanverma-wsu/CVE-2024-41713-Scan · 0 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 6 Dec 2024 (SSVC 2.0.3).
timeline
- 21 Oct 2024Published
- 5 Dec 2024First proof-of-concept repository on GitHub (unvetted) · 44 days later
- 6 Dec 2024CISA SSVC assessment: exploitation active · 1 day later
- 7 Jan 2025Added to CISA KEV (exploited in the wild) · 32 days later
- 28 Jan 2025CISA remediation due date (US federal agencies) · 21 days later
- 4 Aug 2026CVE record last updated · 553 days (about 2 years) later
- 2 Nov 2026Analysed by vulneraibility.com · 91 days (about 3 months) later
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.