# PHP2Shell by platform: CMS, shops, frameworks > Security guides for WordPress, Shopware, TYPO3, Magento, Laravel and other PHP platforms after PHP2Shell. Source: https://phpsos.de/en/plattformen/ 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 WordPress, Shopware, TYPO3, Magento and more: what a platform update achieves, what it does not, and where malicious code typically hides. - [WordPress PHP Vulnerability PHP2Shell: What Site Owners Need to Do](https://phpsos.de/en/plattformen/wordpress/): PHP2Shell is a flaw in PHP, not in WordPress. A WordPress update therefore does not help; what matters is the PHP patch, a restart and a check for backdoors. - [WooCommerce Security: Protecting a Shop With Customer Data After PHP2Shell](https://phpsos.de/en/plattformen/woocommerce/): A WooCommerce shop holds orders, customer accounts and access to payment providers. After PHP2Shell, patched PHP, a clean checkout and checked API access are what count. - [Shopware 6 Vulnerability PHP2Shell: How to Secure Your Shop](https://phpsos.de/en/plattformen/shopware-6/): PHP2Shell reaches Shopware 6 through the server's PHP. What matters are the PHP patch and a restart, followed by a look at .env, plugins, the public directory and API integrations. - [Shopware 5 PHP Version After PHP2Shell: Securing Old Shops](https://phpsos.de/en/plattformen/shopware-5/): Many Shopware 5 shops run on old PHP versions without official updates. After PHP2Shell they need a clear plan: check the status, interim protection, migration. - [Magento Vulnerability PHP2Shell: Securing Magento and Adobe Commerce](https://phpsos.de/en/plattformen/magento-adobe-commerce/): PHP2Shell hits Magento through PHP. Besides the patch and restart, what matters most with Magento is env.php, skimmers in the database and hidden admin accounts. - [TYPO3 PHP Vulnerability PHP2Shell: Securing Websites Properly](https://phpsos.de/en/plattformen/typo3/): TYPO3 websites of public authorities and mid-sized companies run on the same PHP as everyone else. What matters: the PHP patch, a restart, a locked Install Tool and a look into fileadmin. - [Joomla Vulnerability PHP2Shell: Securing Joomla Websites](https://phpsos.de/en/plattformen/joomla/): PHP2Shell affects Joomla through the server's PHP. After the patch and restart, check configuration.php, template overrides, extensions and Super User accounts. - [Drupal PHP Security After PHP2Shell: How to Secure Your Website](https://phpsos.de/en/plattformen/drupal/): Drupal runs on PHP and is therefore affected by PHP2Shell if the server is not patched. What matters: the status report, settings.php, the files folder and role permissions. - [Contao Security After PHP2Shell: Securing Websites Properly](https://phpsos.de/en/plattformen/contao/): Contao runs on PHP and Symfony. After PHP2Shell, what counts is the PHP patch for web and command line, a protected Contao Manager and a look into files and templates. - [PrestaShop Vulnerability PHP2Shell: How to Protect Your Shop](https://phpsos.de/en/plattformen/prestashop/): PHP2Shell hits PrestaShop through the server's PHP. After the patch and restart, the override folder, modules, checkout and employee accounts need to be reviewed. - [OXID eShop Security After PHP2Shell: Securing the Shop and Its Interfaces](https://phpsos.de/en/plattformen/oxid-eshop/): OXID shops in B2B and wholesale are tied to ERP and customer accounts. After PHP2Shell, what counts is the PHP patch, a restart, a look at config.inc.php and modules, and checked admin accounts. - [Laravel Vulnerability PHP2Shell: Securing Applications Properly](https://phpsos.de/en/plattformen/laravel/): PHP2Shell hits Laravel applications through PHP. Besides the patch, what matters most with Laravel are queue workers, Octane, the .env file and the storage folder. - [Symfony Security After PHP2Shell: Securing Projects and Workers](https://phpsos.de/en/plattformen/symfony/): Symfony applications are affected by PHP2Shell through PHP. What matters: patch and restart, including Messenger workers, protected secrets, a clean cache and no profiler in production. - [Nextcloud PHP Vulnerability PHP2Shell: Securing Your File Storage](https://phpsos.de/en/plattformen/nextcloud/): Nextcloud stores contracts, personnel files and project data on a PHP server. After PHP2Shell, what counts is the patch, a restart including cron, an integrity check and a protected data directory. - [Moodle Security After PHP2Shell: Securing Learning Platforms Properly](https://phpsos.de/en/plattformen/moodle/): Moodle manages participant data, grades and exam submissions, often of minors. After PHP2Shell, what counts is the PHP patch, a restart of web and cron, a protected moodledata and checked plugins. - [MediaWiki Security After PHP2Shell: Securing Internal Wikis](https://phpsos.de/en/plattformen/mediawiki/): Internal wikis contain access instructions, procedures and network diagrams. After PHP2Shell, what counts is the PHP patch, a restart, a protected images directory and checked interface administrators. - [Matomo Security After PHP2Shell: Securing Self-Hosted Web Analytics](https://phpsos.de/en/plattformen/matomo/): A compromised Matomo server can deliver malicious code to all tracked websites. After PHP2Shell, what counts is the PHP patch, a restart, and a check of the tracker script and API tokens. - [Craft CMS Security After PHP2Shell: Securing Agency Websites](https://phpsos.de/en/plattformen/craft-cms/): Craft CMS runs on PHP and is often used by agencies with many client sites. After PHP2Shell, what counts is the patch, a restart, a protected security key and a comparison of the Project Config.