dbcve.org
3cxApplication

CVE-2022-48483

HIGH · 7.5 CVSS v3.1 Published 2023-05-02
Fix available
A fix is available. Upgrade to 18.0.3.461 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 Hotfix 1 build 18.0.3.461 on Windows allows unauthenticated remote attackers to read %WINDIR%\system32 files via /Electron/download directory traversal in conjunction with a path component that has a drive letter and uses backslash characters. NOTE: this issue exists because of an incomplete fix for CVE-2022-28005.

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 directory traversal vulnerability in 3CX Web Client (versions before 18 Hotfix 1 build 18.0.3.461 on Windows) allows unauthenticated remote attackers to read arbitrary system files from %WINDIR%\system32 via the /Electron/download endpoint by manipulating path components to include drive letters and backslash characters. This represents an incomplete fix for CVE-2022-28005.

MitigationUpgrade 3CX to version 18 Hotfix 1 build 18.0.3.461 or later. If immediate patching is not feasible, consider restricting access to the /Electron/download endpoint via web server configuration or firewall rules.

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.3.461

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 on Windows
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*3CX*"} | Select-Object DisplayName, DisplayVersion' in PowerShell to retrieve the installed version
    Affected if The displayed version is below 18.0.3.461 (for example, 18.0.0.XXX or 18.0.1.XXX)
  2. Confirm the 3CX management console is accessible
    Attempt to access the 3CX web interface in a browser at https://<your-server>:5001 or the configured port. If the login page loads, the web client is active
    Affected if The web interface is reachable and running on a Windows server
  3. Test for vulnerable endpoint exposure
    Using a web browser or curl, attempt to access https://<your-server>:<port>/Electron/download?filepath=..\..\..\windows\system32\config\sam (or similar path traversal pattern). A successful response containing system file contents indicates the vulnerability is present
    Affected if The server returns file contents from outside the intended download directory, demonstrating the directory traversal is exploitable

A Windows server running 3CX with version below 18.0.3.461 AND with the /Electron/download endpoint accessible indicates the environment is affected by this CVE.

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.3.461 or later
Fixed in 18.0.3.461
Interim mitigation

Upgrade 3CX to version 18 Hotfix 1 build 18.0.3.461 or later. If immediate patching is not feasible, consider restricting access to the /Electron/download endpoint via web server configuration or firewall rules.

Recommended fix High confidence

18.0.3.461 (18 HotFix 1)

  1. Verify current 3CX installation version by checking the 3CX Management Console or installed program information
  2. Download 3CX version 18.0.3.461 (18 HotFix 1) or later from the official 3CX website
  3. Backup the current 3CX configuration and any critical data
  4. Stop the 3CX Phone System service before upgrading
  5. Run the 3CX installer for version 18.0.3.461 or later
  6. Follow the on-screen upgrade installation prompts
  7. Restart the 3CX Phone System service after upgrade completes
  8. Verify the installation was successful and the service is running

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

Fix this in 3cx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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