Some systems are experiencing issues.

Update – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619

Most cloud PBXs have now been updated with the patched PHP versions. A small number remain, and our team is handling them individually. No action is required from partners for cloud PBXs.

All Wildix cloud services remain fully operational.

On-premise PBXs without auto-upgrade enabled should be updated as soon as possible, if this hasn’t been done already.

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 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

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We observe an increased amount of errors coming from the Remote support service. We are investigating.

January 9, at 10:35 CET CLASSOUND Service faced critical call routing issues because of a wrong configuration inserted by human error that caused routing errors in the production clusters.

Recovery of 100 % of incoming routes and 95 % of outgoing routes was achieved by 13:20 CET. 5% of the remaining outgoing routes were restored by 16:30 CET.

The configuration issue was not detected on the stage clusters due to a failure of auto-tests. All necessary improvements are being applied to auto-tests and release procedures to prevent a similar situation from happening in the future.

Service has been restored. Recovery of 100 % of incoming routes and 95 % of outgoing routes was achieved by 11:20 GMT, 5 % of remaining outgoing routes was restored by 14:30 GMT. In case you are still experiencing any issues, please contact our technical support.

We have observed service recovery and finalizing repairs. This incident will be resolved when we confirm all repairs are complete

We involved additional teams in resolving this issue and we also took measures to mitigate the impact of this incident as much as possible.

We are observing an increased number of failed calls and currently working on this issue.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

WMP temporarily is not accessible due to investigation work on it. This indirectly affects multiple services, mostly it affected that requesting new licenses is impossible. We are doing our best to fix this issue ASAP.

We involved additional teams in resolving this issue and we also took measures to mitigate the impact of this incident as much as possible.

We observe increased amount of errors coming from WMP regarding license adjustments. We are investigating.

Wildix will be performing general maintenance of DNS services. During this maintenance window (17/12), we expect to see zero periods of service degradation. We are performing this operation to improve our overall services’ reliability and quality. If you have any questions, please, do not hesitate to reach out to us via our Tech Support teams.

Note that after the migration, it will be impossible to reach PBX using its serial number in FQDN, e.g. 221123456789.wildixin.com.

UPD: Maintenance completed

Case has been resolved. Kindly contact technical support in case you face any performance issues with Zoho service.

Due to emergency maintenance following the potential vulnerability in the Zoho integration, PBXs involved might become unavailable for a few seconds during the next hour.

We detected a potential vulnerability in the Zoho integration which will be disabled for the moment.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We’re currently experiencing degraded performance issues with Wizyconf service. Our team is working to restore normal performance levels.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We’re currently experiencing partial issues with incoming calls in Germany. Our team is working to restore normal performance levels.

Service has been restored. In case you are still experiencing any issues, please contact our technical support.

We’re experiencing a high number of error messages during the license adjustments process. Our team is currently investigating this issue.

Internet connectivity issue for the us-east-2 region has resolved at 09:06 PM UTC. In case you are still experiencing any issues, please contact our technical support.

AWS is having some issues in the US East regions, which are affecting our Cloud PBXs in these areas. We are working with AWS to reduce the impact to a minimum.

The issue has been resolved

We observe some errors about e-mail sending from WMP. We are investigating.

Service has been restored. Please get in touch with our support team if you are still experiencing any issues.

We are experiencing a service outage with the Portal website. Our team is currently working to restore the service.

This maintenance is being rescheduled for a different date. Thank you for your understanding and apologize for any inconvenience.

We will be performing scheduled maintenance on DNS service on 2022-11-19.