dbcve.org
3cxApplication

CVE-2022-48482

HIGH · 7.5 CVSS v3.1 Published 2023-05-02
Fix available
A fix is available. Upgrade to 18.0.2.315 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
3CX before 18 Update 2 Security Hotfix build 18.0.2.315 on Windows allows unauthenticated remote attackers to read certain files via /Electron/download directory traversal. Files may have credentials, full backups, call recordings, and chat logs.

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

A path traversal vulnerability in 3CX VoIP software versions before 18 Update 2 Security Hotfix build 18.0.2.315 on Windows allows unauthenticated remote attackers to access arbitrary files via the /Electron/download endpoint using directory traversal sequences. The vulnerability exposes sensitive data including credentials, full system backups, call recordings, and chat logs.

MitigationApply the vendor patch by updating to 3CX version 18 Update 2 Security Hotfix build 18.0.2.315 or later. If immediate patching is not feasible, restrict network access to the /Electron/download endpoint and monitor for unauthorized access attempts.

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
3cxApplication
Affected:< 18.0.2.315

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed 3CX version
    Locate and inspect the 3CX installation directory. Check for version information in the main executable, installation logs, or the 3CX Management Console under System > About. Compare the build number to 18.0.2.315.
    Affected if The installed version is any build before 18.0.2.315 (e.g., 18.0.0.x, 18.0.1.x, or earlier 18.x versions).
  2. Confirm Windows platform
    Verify that the 3CX software is running on a Windows operating system, as this CVE specifically affects Windows deployments.
    Affected if The 3CX instance is running on Windows.
  3. Check if /Electron/download endpoint is exposed
    From a system with network access to the 3CX server, send an HTTP request to the /Electron/download endpoint (e.g., curl or a browser to https://<3cx-server>/Electron/download). Determine if the endpoint responds or is reachable.
    Affected if The /Electron/download endpoint is accessible from the network without authentication.
  4. Test for directory traversal (optional verification)
    If the endpoint is accessible, attempt a controlled path traversal request such as /Electron/download/../../../../windows/win.ini or similar to verify the vulnerability exists. Only perform this on systems you have authorization to test.
    Affected if The directory traversal sequence returns content from files outside the intended directory, confirming the path traversal vulnerability is active.

A 3CX instance is affected if it runs on Windows, has a version build number lower than 18.0.2.315, and has the /Electron/download endpoint accessible from the network.

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 18.0.2.315 or later
Fixed in 18.0.2.315
Interim mitigation

Apply the vendor patch by updating to 3CX version 18 Update 2 Security Hotfix build 18.0.2.315 or later. If immediate patching is not feasible, restrict network access to the /Electron/download endpoint and monitor for unauthorized access attempts.

Recommended fix High confidence

3CX version 18 Update 2 Security Hotfix build 18.0.2.315 or later

  1. 1. Identify the current 3CX installation version via the management console or Windows Programs list
  2. 2. Download the latest 3CX version 18 Update 2 Security Hotfix (build 18.0.2.315) or later from the official 3CX website at www.3cx.com
  3. 3. Back up the existing 3CX configuration and any critical data before proceeding
  4. 4. Run the 3CX installer to apply the security update
  5. 5. Verify the installation completed successfully and the version shows 18.0.2.315 or higher
  6. 6. Test that the /Electron/download endpoint is patched and no longer allows directory traversal
Caveat Standard upgrade considerations apply - test in non-production first, ensure backups are verified, and schedule during maintenance window

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

Fix this in 3cx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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