Safeguard
Vulnerability Analysis•

CVE-2023-33759: Critical Brute Force Gap in SpliceCom PBX

CVE-2023-33759: SpliceCom Maximiser Soft PBX did not limit failed logins, so short PINs can be guessed. Turn on Access Control and verify your version.

Safeguard Security Team
3 min read

CVE-2023-33759 is a critical (CVSS 9.8) flaw in SpliceCom Maximiser Soft PBX: failed logins to the remote gateway are not rate limited, so short numeric passcodes can be guessed. The record says version 1.5 and before. Turn on the Access Control feature and confirm your version with the vendor.

What's affected

  • SpliceCom Maximiser Soft PBX v1.5 and before, according to the NVD record.
  • The researcher write-up says rate limiting and IP banning arrived as an Access Control feature starting with version 1.5, but that it is not enabled by default.
  • The weakness affects the remote SSL Gateway, which lets mobile and remote users connect to the PBX.

The weakness class is CWE-307, improper restriction of excessive authentication attempts.

How to check if you're exposed

Ask your telephony administrator or provider for the Maximiser Soft PBX version and for the status of the Access Control feature on the SSL Gateway. There is no public command we can point to for this, so the vendor or hosting provider is the right source.

Also check how remote users authenticate. The researcher notes describe an extension number plus a short passcode, which is often numeric. If your remote users have four digit passcodes, assume they are guessable without rate limiting.

Review gateway and PBX logs for long runs of failed logins from one address, and for logins from addresses you do not expect.

What to do now

  1. Confirm your Maximiser Soft PBX version with SpliceCom or your hosting provider, and ask which release carries the fix.
  2. Enable the Access Control feature for rate limiting and IP banning on the SSL Gateway, and verify it works with a test.
  3. Move remote users to longer passcodes. Short numeric PINs fall quickly once guessing is not slowed.
  4. Restrict the gateway to known source addresses or place it behind a VPN where your design allows.
  5. Review call logs and billing for unexpected outbound calls, which can show a compromised extension.

If you track software dependencies, the free in-browser dependency scan can show which of your components carry known CVEs, and the Gold directory lists the same records in one place.

Why it matters

When a login system lets anyone retry forever, the strength of the secret is all that stands in the way. A four digit passcode has only ten thousand possibilities. The researcher states that all four digit combinations could be tried in around 90 seconds without rate limiting, and that extension numbers are often sequential and easy to find.

Telephony is an attractive target because a hijacked extension can place calls on someone else's account. The fix is layered: limit attempts, ban repeat sources, use longer secrets, and keep the gateway off open networks.

The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog. The researcher published a proof of concept tool, which we do not describe here.

Quick check

Why is a brute force issue rated critical?

The NVD vector scores it as network reachable, no privileges, no user interaction, with high impact. Successful guessing yields access to a PBX account.

Does version 1.5 fix it?

Sources differ. NVD says 1.5 and before are affected. The researcher says 1.5 added an Access Control feature that is off by default. Treat 1.5 as fixed only if the feature is on.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.