# CVE-2023-33760: Weak cryptography in n/a

> Attackers can eavesdrop on communications via man-in-the-middle attacks due to the use of a default SSL certificate in the Soft PBX system.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-xr44-2pv4-gw8r

## What is CVE-2023-33760?

CVE-2023-33760 is a medium-severity vulnerability in n/a, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SpliceCom Maximiser Soft PBX v1.5 and before was discovered to utilize a default SSL certificate. This issue can allow attackers to eavesdrop on communications via a man-in-the-middle attack.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2023-33760?

It affects 1 product.


Products: Splicecom Maximiser Soft Pbx.

## How do I fix CVE-2023-33760?

No fix has been published for CVE-2023-33760 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-33760 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33760 exists.

## Other vulnerabilities in n/a

- [CVE-2023-33759](https://insights.sbomify.com/CVE-2023-33759/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-33758](https://insights.sbomify.com/CVE-2023-33758/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33760 and fix it if it is affected.

What it is: CVE-2023-33760 is a medium-severity vulnerability in n/a, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33760 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-33760/ (Markdown: https://insights.sbomify.com/CVE-2023-33760/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33760
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33760
- OSV: https://osv.dev/vulnerability/CVE-2023-33760

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-33760/
Summaries are generated and may contain mistakes; the official description above is the record.