Dev.to Security 🔐 Cybersecurity 👁 0 📖 2 min read

FusionPBX's 10,653 App Matches Sit on a Multi-Tenant Voice Control Plane

FusionPBX's 10,653 App Matches Sit on a Multi-Tenant Voice Control Plane FusionPBX is a web administration layer for FreeSWITCH. The product documentation describes domain-based multi-tenancy, users, extensions, gatewa

FusionPBX's 10,653 App Matches Sit on a Multi-Tenant Voice Control Plane

FusionPBX is a web administration layer for FreeSWITCH. The product documentation describes domain-based multi-tenancy, users, extensions, gateways, devices, call routing and group permissions. It is a control plane for voice services, not a simple static website.

ZoomEye count-only queries on 2026-11-18 returned 10,653 matches for app="FusionPBX" and 10,600 for title="FusionPBX". The near-equal application and title counts are useful because they reduce, though do not eliminate, the chance that the title query is dominated by unrelated pages. They still do not show whether a deployment is a login page, a public portal, a broken instance or a management interface with weak tenant separation.

Tenant boundaries live in several systems

FusionPBX domains separate organizations, users and extensions. Group permissions decide which administrative functions a logged-in user can reach. FreeSWITCH has its own XML RPC and event socket paths. The web layer, the SIP layer and the telephony engine can each expose authority that the others do not expect.

FusionPBX's security documentation recommends keeping XML RPC port 8787 off the public network and using a VPN if remote access is needed. That is an important distinction from the HTTPS login page. A deployment can have a well-protected dashboard and an exposed control port that changes the underlying switch configuration.

The group manager should be reviewed across domains. An administrator in one domain should not be able to select another domain's extensions or gateways through a manipulated identifier. Device provisioning, call recordings, voicemail and outbound routes may each have their own permission path. The web application should enforce the tenant boundary on every object lookup.

Inventory the phone and the portal

An external count of FusionPBX does not identify the PBX users, phone numbers or SIP registrations behind it. Those are separate assets. Search inventory for HTTPS dashboards, SIP listeners, provisioning endpoints and XML RPC ports. Keep the results in the same ownership record, but give each service its own exposure decision.

The public dashboard should require strong authentication, rate limiting and a network policy appropriate to its users. If the dashboard is only for administrators, place it behind a VPN or identity-aware proxy. If it serves end users, separate that route from administrative functions and test role boundaries with accounts from at least two domains.

Monitor authentication failures, permission changes, new admin users and failed provisioning attempts. A successful login at the portal is not evidence that the tenant boundary is correct. The more useful test is whether a user from domain A can read or change an object in domain B by changing a request parameter.

The 10,653 application matches describe a large observable population of a multi-tenant voice platform. They do not prove that those systems are misconfigured. The review should focus on the control paths that can alter calls, credentials and tenant data.

References

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.