dbcve.org
CompletepbxApplication · Xorcom

CVE-2025-30006

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 5.2.36.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 reflected cross-site scripting (XSS) in the administrative control panel. 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 · moderate confidence

Reflected cross-site scripting (XSS) vulnerability in Xorcom CompletePBX administrative control panel. The vulnerability allows attackers to inject malicious scripts through user input that is immediately reflected in the web response without proper sanitization or output encoding.

MitigationImplement proper input validation and output encoding for all user-supplied data in the administrative control panel. Additionally, set appropriate Content-Type headers and consider implementing Content Security Policy (CSP) to mitigate XSS risks.

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

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

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. Identify CompletePBX version
    Access the administrative control panel and locate the version information, typically found in the system status, about, or settings page. Alternatively, check system files or the web interface footer for the installed version number.
    Affected if The displayed version is below 5.2.36.1 (for example, 5.2.35.x or earlier)
  2. Verify admin control panel is accessible
    Confirm the CompletePBX administrative web interface is reachable by accessing the panel URL (commonly /admin, /webconfig, or the primary login page).
    Affected if The admin control panel is accessible over the network (local or remote)
  3. Check for reflected user input in responses
    Submit a test string containing non-malicious characters (such as <test>) through common admin panel input fields (search, forms, parameters in URL). Observe whether this string is reflected verbatim in the subsequent web page response without encoding.
    Affected if User-supplied input appears unescaped in the HTML response (for example, entering <test> displays as <test> rather than &lt;test&gt;) on a vulnerable version below 5.2.36.1

A user is affected if their CompletePBX installation is version 5.2.36.0 or lower AND the administrative control panel is accessible, with user input being reflected without proper encoding.

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

Implement proper input validation and output encoding for all user-supplied data in the administrative control panel. Additionally, set appropriate Content-Type headers and consider implementing Content Security Policy (CSP) to mitigate XSS risks.

Recommended fix Moderate confidence

CompletePBX version 5.2.36.1 or later

  1. 1. Back up the current CompletePBX configuration and all critical data
  2. 2. Review the Xorcom CompletePBX release notes for version 5.2.36.1 to understand changes
  3. 3. Download the version 5.2.36.1 (or latest stable 5.2.x) update package from the official Xorcom download portal at xorcom.com
  4. 4. Schedule a maintenance window as the upgrade may require brief downtime
  5. 5. Apply the upgrade following the standard CompletePBX upgrade procedure documented in the admin guide
  6. 6. After upgrade, verify the administrative control panel is accessible and functioning
  7. 7. Clear browser cache to ensure no stale resources are loaded
  8. 8. Confirm the XSS vulnerability is resolved by testing the previously affected parameter

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

Fix this in Completepbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30006 — 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-30006 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