Wildix Integrations Hub has been taken offline as a precaution following the disclosure of critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 (known as PHP2Shell). We know this interrupts any workflows that depend on the integrations, and we’re sorry for the disruption. We concluded that keeping the service offline until the fixes are applied is necessary to protect your data and our infrastructure.
While the service is offline, integrations configured through Wildix Integrations Hub will not sync or run. Other PBX features are not affected.
We expect the service to be available again later today and will post an update here as soon as it is restored.
For details on the vulnerabilities, see PHP’s security advisory: https://www.php.net/archive/2026.php#2026-10-21-5
We are carrying out urgent security work following the disclosure of vulnerabilities affecting certain PHP-based services. As a precaution, access to some Wildix services may be temporarily unavailable while we apply protective measures and investigate potential exposure. We will post further updates here as work progresses and we can confirm the impact and recovery timelines.
For more information about this vulnerability, please refer to the CERT-EU security advisory: https://cert.europa.eu/publications/security-advisories/2026-018
Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619
All Wildix cloud services have been updated with the patched PHP versions and are fully operational, including Legacy Kite, Legacy File Sharing, Zoho Integration Service and Wildix Integrations Hub. The rollout to cloud PBXs is in progress. No action is required from partners.
On-premise PBXs without auto-upgrade enabled should be updated as soon as possible, if this hasn’t been done already.
We will post a final update once the cloud PBX rollout is complete.
Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619
On 21 October 2026, the PHP project disclosed two critical vulnerabilities in the PHP runtime, CVE-2026-109618 and CVE-2026-109619 (CVSS 4.0: 9.2). Both could allow remote code execution without authentication. PHP has released fixed versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP’s advisory: https://www.php.net/archive/2026.php#2026-10-21-5
Wildix PBX
Supported PBX versions run on PHP 8.2 (WMS 6 and WMS 7 up to 7.08) and 8.4 (WMS 7.09 and later). Patched packages for on-premise PBXs are available in all Wildix repositories.
• Cloud PBXs: The update is being rolled out by Wildix. No action is required from partners. We will post an update here once the rollout is complete.
• On-premise PBXs with auto-upgrade enabled will receive the update automatically.
• On-premise PBXs without auto-upgrade must be updated manually as soon as possible.
• PBXs on versions older than WMS 6 must be upgraded to WMS 6 or WMS 7 as soon as possible.
Wildix services Our teams are applying the patched version across our infrastructure.
As a precaution, the following services have been taken offline until patching is complete:
•Legacy Kite •Legacy File Sharing •Zoho Integration Service •Wildix Integrations Hub
Other PBX features are not affected by this maintenance.
We will post further updates here as services are restored.
Wildix Integrations Hub has been taken offline as a precaution following the disclosure of critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 (known as PHP2Shell). We know this interrupts any workflows that depend on the integrations, and we’re sorry for the disruption. We concluded that keeping the service offline until the fixes are applied is necessary to protect your data and our infrastructure.
While the service is offline, integrations configured through Wildix Integrations Hub will not sync or run. Other PBX features are not affected.
We expect the service to be available again later today and will post an update here as soon as it is restored.
For details on the vulnerabilities, see PHP’s security advisory: https://www.php.net/archive/2026.php#2026-10-21-5
We are carrying out urgent security work following the disclosure of vulnerabilities affecting certain PHP-based services. As a precaution, access to some Wildix services may be temporarily unavailable while we apply protective measures and investigate potential exposure. We will post further updates here as work progresses and we can confirm the impact and recovery timelines.
For more information about this vulnerability, please refer to the CERT-EU security advisory: https://cert.europa.eu/publications/security-advisories/2026-018
Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619
All Wildix cloud services have been updated with the patched PHP versions and are fully operational, including Legacy Kite, Legacy File Sharing, Zoho Integration Service and Wildix Integrations Hub. The rollout to cloud PBXs is in progress. No action is required from partners.
On-premise PBXs without auto-upgrade enabled should be updated as soon as possible, if this hasn’t been done already.
We will post a final update once the cloud PBX rollout is complete.
Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619
On 21 October 2026, the PHP project disclosed two critical vulnerabilities in the PHP runtime, CVE-2026-109618 and CVE-2026-109619 (CVSS 4.0: 9.2). Both could allow remote code execution without authentication. PHP has released fixed versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP’s advisory: https://www.php.net/archive/2026.php#2026-10-21-5
Wildix PBX
Supported PBX versions run on PHP 8.2 (WMS 6 and WMS 7 up to 7.08) and 8.4 (WMS 7.09 and later). Patched packages for on-premise PBXs are available in all Wildix repositories.
• Cloud PBXs: The update is being rolled out by Wildix. No action is required from partners. We will post an update here once the rollout is complete.
• On-premise PBXs with auto-upgrade enabled will receive the update automatically.
• On-premise PBXs without auto-upgrade must be updated manually as soon as possible.
• PBXs on versions older than WMS 6 must be upgraded to WMS 6 or WMS 7 as soon as possible.
Wildix services Our teams are applying the patched version across our infrastructure.
As a precaution, the following services have been taken offline until patching is complete:
•Legacy Kite •Legacy File Sharing •Zoho Integration Service •Wildix Integrations Hub
Other PBX features are not affected by this maintenance.
We will post further updates here as services are restored.
We are currently experiencing degraded performance affecting the Push service. Our team is investigating the issue and working to restore normal service performance.
We will be performing scheduled maintenance on Wizyconf Conferences on 17-10-2026 07:00-08:00 UTC timezone During this time some services might be temporarily unavailable.
The CDS service will be unavailable due to scheduled maintenance on Saturday, October 3, 2026, from 06:00 AM UTC to 07:00 AM UTC.
We are currently seeing a small increase in the number of errors from PBXs. Our team is investigating the issue and working to restore normal service.
We will provide further updates as soon as possible.
We are currently experiencing an issue affecting Chat AI Agents. Our team is investigating the root cause and working to restore normal service. We will provide further updates as more information becomes available.
Salesforce Partner Community is currently experiencing an outage. We will provide updates as soon as more information is available.
Salesforce Partner Community service has been restored and is operating normally. This incident is now resolved.
Salesforce is currently experiencing another service disruption. We are monitoring the situation and will provide further updates as they become available.
Service has been restored and is currently operating normally. If you experience any problems, please contact our Technical Support team.
We are currently experiencing performance issues with the Microsoft Teams Presence integration. Our team is investigating the root cause.
We will be performing scheduled maintenance on TTS services on 10.09.2026 16:00-17:00 UTC timezone During this time some services might be temporarily unavailable.
We will be performing scheduled maintenance on TTS, and Geolocation services on 10.09.2026 11:00-12:00 UTC timezone During this time some services might be temporarily unavailable.
We will be performing scheduled maintenance on TTS, STT, URL preview, Authorization and Geolocation services on 10.09.2026 06:00-07:00 UTC timezone During this time some services might be temporarily unavailable.
We will be performing scheduled maintenance on Wizyconf Conferences on 05.09.2026 07:00-08:00 UTC time zone During this time some services might be temporarily unavailable.
We are currently experiencing an issue on our website wildix.com. Our team is actively investigating the root cause to restore normal access as swiftly as possible.
We are currently experiencing issues with the SMS service in the US/Canada zone. The wms6 sms services are affected. Our team is working closely with the local representative to restore service as soon as possible. We apologize for the inconvenience.
We will be performing scheduled maintenance on Authorization Service on 12.08.2026 19:00-19:10 UTC timezone. During this time service might be temporarily unavailable.
As part of our ongoing security improvements, the legacy SSL Certificate Service v1 is scheduled to be retired on Saturday, August 1, 2026.
Impact: After this date, PBXs running versions earlier than 6.04 will no longer be able to obtain or renew SSL certificates automatically.
PBXs running version 6.04 or later are not affected.
Customers and partners currently using PBXs older than version 6.04 have time to upgrade before the retirement date. We strongly recommend completing the upgrade in advance to ensure uninterrupted SSL certificate issuance and renewal.
CLASSOUND is currently experiencing a partial outage affecting inbound call capabilities in certain regions of USA. As a result, some incoming calls may not reach the PBX.
Our technical team is actively working to resolve the issue as quickly as possible.
We are currently experiencing performance issues with WMP (Portal), which may result in some PBXs being temporarily unreachable. Our team is working on resolving the issue.
We are performing maintenance on the Portal (WMP). During the time of the maintenance, some services may be temporarily unavailable.
We will be performing scheduled maintenance on Poral on 02.07.2026 04:00-05:00 UTC time zone During this time some services might be temporarily unavailable.
We are investigating an issue affecting systems upgraded from rel70beta. While the issue is under investigation, please do not switch repositories to rel70beta! Our development team is actively working on the issue. We will provide an update as soon as more information is available.
The issue affecting upgrades from rel70beta has been resolved.
All affected PBXs have been restored. We are closing this incident.
The issue affecting new upgrades from rel70beta has been fixed.
We are currently recovering the instances that were affected by the issue. Our team will provide another update once recovery is complete.
One of CLASSOUND local lines is currently experiencing an outage with terminating inbound calls traffic to +3904 dial codes numbers in Italy
Our technical team is actively working to resolve this issue as quickly as possible.
Service has been restored. In case you are still experiencing any issues, please contact our technical support.
[CLASSOUND] Partial Inbound Calls Outage to Italy +3904 Prefixes — Status Update
Status update on the ongoing partial inbound calls outage affecting inbound calls to numbers with +3904 dial codes in Italy.
The fault has been localized: civil infrastructure near the Peschiera del Garda toll gate (approximately 3 km from Desenzano) has been damaged and is currently being addressed by local services. The repair team is already on site, and restoration efforts are underway—a new cable section is being installed.
The estimated time for restoration (ETR) is 14:00 GMT.
Our technical team remains in close contact with local services and will inform you about further progress on the resolution as soon as possible.
We will be performing scheduled maintenance on Wizyconf on Saturday, 2026-06-20, 7:00 - 8:00 AM UTC time. During this time some services might be temporarily unavailable.
We are currently experiencing an outage affecting WhatsApp messages. The issue is under investigation. We will provide updates as soon as more information is available.
We will be performing scheduled maintenance on STT and TTS services on 2026-06-20, 07:00 - 08:00 UTC. During this time some features might be temporarily unavailable.
We have identified an issue affecting Microsoft SSO login for users signing in with personal Microsoft accounts.
Users with personal, non-corporate Microsoft accounts may be unable to complete authorization and may see errors such as “Failed to get user info,” “Authorization_RequestDenied,” or “UnknownError.”
Our team is working on a fix. We will provide another update once the fix is ready or deployed.
CLASSOUND is currently experiencing a partial outage affecting inbound call capabilities in certain regions of Germany. As a result, some incoming calls may not reach the PBX.
Our technical team is actively working to resolve the issue as quickly as possible.
CLASSOUND is currently experiencing a partial outage affecting inbound call capabilities in certain regions of Italy (+39). As a result, some incoming calls may not reach the PBX.
Our technical team is actively working to resolve the issue as quickly as possible.
We’re currently experiencing degraded performance issues with SSL Certification Service. Our team is working to restore normal performance levels.
We’re currently experiencing degraded performance issues with SSL Certification Service. Our team is working to restore normal performance levels.
We will be performing scheduled maintenance on Authorization Service on 23.05.2026 06:00-07:00 UTC timezone. During this time service might be temporarily unavailable.
Some PBXs unreachable in Paris region.
The issue affecting PBX availability in the Paris region has been fully resolved.
During the incident, a subset of PBX instances experienced intermittent connectivity issues, which led to temporary unreachability.
Our team identified the root cause and implemented mitigation measures to restore stable operation. We are continuing to monitor the systems closely to ensure consistent performance.
We appreciate your patience while we worked to resolve this issue.