PHP2Shell: The Critical Bug Your WordPress Update Will Not Fix
• 3 min read • Ahmed Daoudi
Most PHP security news is about a plugin. This one is different. PHP2Shell is the nickname for two critical vulnerabilities in the PHP interpreter itself, and because the bugs live below your application, the usual "update WordPress and the plugins" routine does not touch them.
The timeline
- October 21, 2026: the PHP project published emergency releases fixing CVE-2026-109618 and CVE-2026-109619. Sysdig's analysis says the two CVEs cover four related memory-safety bugs, each scored 9.2 on CVSS v4.0.
- October 24: honeypots recorded attackers achieving code execution on unpatched servers.
- October 26: CISA added both CVEs to its Known Exploited Vulnerabilities catalog and gave US federal agencies until October 29 to patch.
Why it is so serious
The flaws can be triggered by an unauthenticated web request and lead to remote code execution before any of your application code runs. Your login page, your web application firewall rules written for WordPress, your carefully reviewed plugin list: none of that is in the path. Since PHP still runs a very large share of the web, the exposed population is huge, and much of it is small business sites that nobody actively maintains.
Where unpatched PHP hides
- Docker images built months ago from a
php:8.xtag and never rebuilt. The tag moved on, your image did not. - Shared hosting where the provider controls the PHP version. Check their status page or ask them directly.
- Linux distribution packages, where the fix may arrive as a backport without the upstream version number changing. Check your distro's security tracker, not just
php -v. - Internal tools and forgotten admin panels on old VMs that nobody remembers owning.
What to do now
- Inventory every place PHP runs, including containers and CI images.
- Upgrade to the patched releases listed in the PHP project's advisory, or the fixed package from your distribution.
- Rebuild and redeploy container images from fresh base images.
- If a server was exposed and unpatched after October 24, assume compromise: look for unfamiliar files in web roots, unexpected cron jobs and outbound connections.
- Rotate secrets those servers could read: database passwords, API keys, cloud credentials.
The broader lesson
We treat the language runtime as part of the floor, something that is just there. PHP2Shell is a reminder that the runtime is a dependency like any other, with a version, a patch cadence and an owner. If nobody on your team can say which PHP version production is running right now, that is the first thing to fix.