CVE-2025-52913
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 · uneditedA vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP2 (9.8.2.12) 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.
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 confidenceA critical path traversal vulnerability exists in Mitel MiCollab's NuPoint Unified Messaging component. The flaw allows unauthenticated attackers to manipulate file path inputs using directory traversal sequences (e.g., ../) to access files outside the intended web root, potentially exposing sensitive user data and system configurations.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify MiCollab installation and versionLocate the MiCollab installation directory or check system inventory for Mitel MiCollab. Obtain the exact version number (e.g., via installed software list, about page, or system configuration).Affected if The installed version is 9.8.2.12 or earlier (any version up to and including 9.8 SP2).
-
Confirm NuPoint Unified Messaging component is enabledAccess the MiCollab administration interface or check system configuration to determine whether the NuPoint Unified Messaging (NPM) component is installed and active.Affected if The NPM component is present and enabled on the system.
-
Determine if NPM web interface is network-accessibleCheck network configuration, firewall rules, or access the NPM web portal URL (typically on ports 443, 80, or 8443) from an external or untrusted network segment to verify accessibility.Affected if The NPM component is exposed to untrusted networks without proper access controls.
-
Review access logs for anomalous path traversal requestsExamine NPM web server access logs for requests containing '../' sequences or unusual file path patterns (e.g., ../../etc/passwd, ../../conf/*).Affected if Suspicious traversal patterns are present in logs, indicating potential exploitation attempts.
You are affected if MiCollab with NuPoint Unified Messaging version 9.8.2.12 or earlier is installed, the NPM component is enabled, and it is accessible over the network.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patch for MiCollab when available. Until then, restrict network access to the NPM component, implement WAF rules to block traversal sequences in requests, and validate all file path inputs on any exposed interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52913 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52913 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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