If your association runs WordPress, there is a good chance a security plugin sent you a reassuring summary this week. Firewall active, no threats blocked, scan clean. If you run Drupal, your status report probably looks fine too.
For PHP2Shell, none of that tells you anything. The attack happens while PHP is still reading the incoming request, before WordPress or Drupal has loaded, which means before any plugin or module exists to notice it. A green dashboard this week is not evidence that your site was safe. It is evidence that the dashboard was looking somewhere else.
Where this comes from. The PHP project's advisory and the two GitHub security advisories, Amazon's threat intelligence report, the PHP manual, and published statements from security vendors that sell WordPress protection, all read directly.
Why Plugins and Modules Cannot See It
The PHP project describes a demonstrated exploit in which a single unauthenticated request triggers the attack before any application code runs. WordPress plugins and Drupal modules are application code. So are the firewalls built into security plugins. They start after PHP has already processed the request that carries the attack.
The vendors say so themselves. MalCare, which sells a WordPress security plugin, said it plainly in its own advisory: its firewall can only inspect a request after PHP has started and loaded WordPress, and the attack fires before that. Sucuri, another WordPress security company, said updating your CMS, plugins, themes or application code does not patch these vulnerabilities.
This is not a failure of those products. It is the wrong layer for this problem. The fix lives on the server, in the PHP version your host runs, and nothing you can install in the WordPress dashboard or the Drupal admin reaches that far down.
You Do Not Need an Upload Form to Be Exposed
Associations often assume this applies only to sites that accept file uploads, such as membership applications, abstract submissions or document portals. It does not. By default PHP reads and parses an incoming upload for any request to any PHP page, filling in its file data before your site's code ever runs. The flaws sit in that parsing. Whether your site has an upload form is irrelevant.
What Does Help, and Its Catch
A patched PHP release is the only complete fix: 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or later. That comes from your host or whoever manages your server.
A firewall in front of the site can help. Security services that sit in front of your site, like Cloudflare or Sucuri's firewall, see the request before PHP does, and both have published rules for known attack patterns. Cloudflare says its rules are on by default, but paid plans should confirm its managed ruleset is set to block. Both companies are clear that this does not replace patching. And there is a condition most association sites never check: the rules only help if your server accepts traffic exclusively through that service. If your site can still be reached directly at its server address, an attacker can simply go around the firewall.
If Something Got In, Here Is Where It Would Be
The GitHub advisory describes the impact as remote code execution as the web worker account. That is the account your site's code runs as, and it can read the same configuration files your site reads, including the database password. Amazon recorded attack attempts from October 17, four days before the fix, and says investigations should start from that date.
- On WordPress, look for. New administrator accounts nobody created. Plugins you do not recognize. PHP files inside the uploads folder, which should only ever hold images and documents. Changes to core files or to the main configuration file. Scheduled tasks nobody set up.
- On Drupal, look for. New users with the administrator role. Modules enabled that nobody turned on. PHP files in the public files directory, which should never contain any. Changes to settings.php.
- On either. If you find any of those, assume the database password and any API keys stored in configuration were read, and change them after the server is patched, not before.
A note on scanners. A file scanner run now can help find what was left behind. It could not have stopped the attack, and if something did get in, it had the same access to the scanner's files as to everything else. Treat a clean scan as useful, not as proof.
Three Questions You Cannot Answer From the Dashboard
Which PHP version is every environment running, and has your host confirmed the patch in writing? Can your site be reached around its firewall or CDN? And has anyone looked at the server, not the plugin, for changes since October 17?
Most associations cannot answer any of the three this week, and that is not a criticism. Nobody set them up to. They are server questions, and the tools most organizations were given only see the website.
If You Do One Thing This Week
Ask your host, in writing, which PHP version every environment runs: live, staging, development, and any old copy still online. That one answer tells you whether the rest of this post applies to you. If the answer is vague, or slow, treat that as a no.
Have us check your site for PHP2Shell
Send us your site address. We will confirm the PHP version on every environment with your host, check whether your site can be reached around its firewall or CDN, and look for changes on the server since October 17. You get a plain answer on where you stand and what to fix first.