dbcve.org
CompletepbxApplication · Xorcom

CVE-2025-30005

HIGH · 8.3 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 5.2.36.1 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Xorcom CompletePBX is vulnerable to a path traversal via the Diagnostics reporting module, which will allow reading of arbitrary files and additionally delete any retrieved file in place of the expected report. This issue affects CompletePBX: all versions up to and prior to 5.2.35

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 confidence

Xorcom CompletePBX contains a path traversal vulnerability in its Diagnostics reporting module. An attacker can exploit this to read arbitrary files on the system by manipulating file path inputs, and can additionally delete any retrieved files in place of the expected diagnostic report output.

MitigationUpgrade to CompletePBX version 5.2.35 or later which contains the patch. Until then, restrict access to the Diagnostics reporting module to trusted users only and monitor for suspicious file access patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CompletepbxApplication
Affected:< 5.2.36.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check CompletePBX installed version
    Use the system version command or check /etc/version file to determine the installed CompletePBX version
    Affected if The installed version is less than 5.2.36.1 (or 5.2.35 depending on the patch version - verify against official release notes)
  2. Verify Diagnostics reporting module status
    Check if the Diagnostics module is enabled and accessible on the system - look for web endpoints or CLI tools related to diagnostics reporting
    Affected if The Diagnostics reporting module is enabled and exposed to network users
  3. Review module access controls
    Inspect access control configurations for the Diagnostics module to determine if it is restricted to trusted users only
    Affected if The Diagnostics module allows access from untrusted networks or users without authentication
  4. Audit recent Diagnostics module access logs
    Review system and web server logs for requests to the Diagnostics reporting feature, focusing on unusual file path patterns
    Affected if Log entries show path traversal attempts (e.g., ../../etc/passwd) or requests for system files through the Diagnostics module

You are affected if your CompletePBX version is below 5.2.36.1 and the Diagnostics reporting module is accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 5.2.36.1 or later
Fixed in 5.2.36.1
Interim mitigation

Upgrade to CompletePBX version 5.2.35 or later which contains the patch. Until then, restrict access to the Diagnostics reporting module to trusted users only and monitor for suspicious file access patterns.

Recommended fix Moderate confidence

5.2.36.1 or later

  1. 1. Identify the current installed version of CompletePBX by checking the system administration interface or running the appropriate version command.
  2. 2. Obtain the CompletePBX version 5.2.36.1 or later from the official Xorcom distribution channels.
  3. 3. Perform a full backup of the CompletePBX system including all configurations, recordings, and call data before upgrading.
  4. 4. Execute the upgrade to version 5.2.36.1 or later following the standard CompletePBX upgrade procedure documented by Xorcom.
  5. 5. After upgrade completion, verify the Diagnostics reporting module is functioning correctly and that path traversal restrictions are enforced.
  6. 6. Confirm the new version is running by checking the system version information.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Completepbx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30005 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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