<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PHP on Hadosec — Application &amp; AI Security for SMEs</title><link>https://www.hadosec.com/tags/php/</link><description>Recent content in PHP on Hadosec — Application &amp; AI Security for SMEs</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.hadosec.com/tags/php/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP2Shell: How to Protect Your Website From the Critical New PHP Vulnerability</title><link>https://www.hadosec.com/blog/php2shell-critical-php-vulnerability/</link><pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.hadosec.com/blog/php2shell-critical-php-vulnerability/</guid><description>&lt;p&gt;On 21 October 2026, the PHP project shipped emergency patches for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, now known together by the name security researchers gave them: &lt;strong&gt;PHP2Shell&lt;/strong&gt;. Both let an attacker take over a web server remotely, with no password and no user interaction, and together they affect software running roughly 70% of all websites on the internet. If you run PHP anywhere, directly or through WordPress, Drupal, Joomla, or Magento, this post explains what happened, what the jargon means, and exactly what to do about it.&lt;/p&gt;</description></item></channel></rss>