CVE-2023-27362 is a local privilege escalation in 3CX. The product loads an OpenSSL configuration file from an unsecured location, so a low-privileged user can run code as SYSTEM. NVD scores it 7.8, High. The record points to the 3CX version 18 Update 8 release notes for the fix, which you should confirm.
What's affected
The record lists the 3CX product without a version range. It cites the 3CX release page for version 18 Update 8, which suggests that release addresses the issue. I could not retrieve that page (the site returned an access denied response), so I cannot confirm the exact fixed build from the vendor text.
Check the 3CX release notes for your branch before you decide you are safe. Treat any 3CX Windows server older than version 18 Update 8 as needing review, and read the notes for later releases too.
No severity conflict: the record scores it 7.8, High, and I found no second score.
How to check if you're exposed
Open the 3CX management console and note the installed version, or check the application version in Windows under installed programs on the server. Compare it with the release notes on the 3CX site.
Next, look at who can log on to the 3CX host. The attack needs the ability to run low-privileged code on the machine first, so shared servers and hosts used for remote desktop sessions are the places to review.
What to do now
- Update 3CX to the current release for your branch, and confirm the fix in the vendor notes for version 18 Update 8 or later.
- Limit interactive logons to the 3CX server to administrators only.
- Check which accounts can write to the folders the 3CX service reads configuration from.
- Keep endpoint monitoring on the host so unusual child processes of the 3CX service are visible.
- Follow the Gold page for this CVE for any update to the references.
Why it matters
The record says the product loads an OpenSSL configuration file from an unsecured location. The weakness class is CWE-427 (Uncontrolled Search Path Element), uncontrolled search path. If a program looks for a file in a place a normal user can write to, that user can put their own file there and have the privileged program read it.
This is a local issue, so it matters most after something else has gone wrong, such as a phished staff account or another bug. It turns a small foothold into full control of the machine. Phone system servers also hold call records and credentials for trunks, which is a reason to keep them on a tight update schedule.
Quick check
Can someone exploit this from the internet?
Not directly. The record says the attacker must first be able to run low-privileged code on the target.
Sources
- 3CX version 18 Update 8 release notes (cited by the record; could not be retrieved)
- Zero Day Initiative advisory ZDI-23-1153
Last reviewed: 19 October 2026.