# PHP SOS: PHP emergency help and server security

> Remote emergency help for PHP2Shell and server attacks for businesses in Europe.

Source: https://phpsos.de/en/  
As of: 25/10/2026  
Provider: PHP SOS, PHP emergency help and server security. Immediate help via WhatsApp: https://wa.me/491736494914?text=Hello%20PHP%20SOS%2C%20we%20need%20help%20with%20our%20PHP%20server.%20Company%3A%20%E2%80%A6%20Website%3A%20%E2%80%A6

PHP SOS helps businesses in Europe remotely with PHP vulnerabilities such as PHP2Shell (CVE-2026-109618, CVE-2026-109619): patching PHP and documenting the restart, checking for signs of intrusion, removing malicious code, hardening the server, and reporting for management, data protection and insurance.

## Frequently asked questions

**What is PHP2Shell?**  
PHP2Shell is the name for two critical vulnerabilities in PHP itself (CVE-2026-109618 and CVE-2026-109619, CVSS 9.2). They may allow attackers to execute malicious code on the server without logging in. Patches have been available since 21 October 2026.

**Which PHP versions are safe?**  
The fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Hosts and distributions sometimes apply backports without changing the version number. What matters is the package version or the provider's written confirmation.

**Is a WordPress or shop update enough?**  
No. The vulnerability is in PHP, not in the CMS. A CMS update does not close it. And a PHP patch does not remove malicious code that was planted beforehand.

**How quickly can you help?**  
We work remotely and start as soon as access is in place. Write to us via WhatsApp with your system, PHP version and observation. We will then clarify the approach directly.

**Do you also work for agencies and hosting customers?**  
Yes. We work directly for businesses, in the background on behalf of agencies, and in coordination with your host if the host manages the server.

**Do we have to report the incident?**  
If personal data may be affected, Art. 33 GDPR generally sets a reporting deadline of 72 hours from awareness. Whether it applies, you clarify with your data protection officer. We provide the technical documentation for it.
