• Terms of Service

Learn Internet Grow

Tech Skills

  • Learn
  • Books
  • Search
  • Create
  • Measure
  • Secure
  • Share
  • Terms of Service

PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do.

Filed Under: Secure

PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do — a painterly illustration conveying this idea from "PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do."

On 21 October 2026 the PHP project released an emergency PHP security update for two critical flaws, and the headlines that followed were some of the loudest in years. If you own a WordPress site, the useful news is smaller and much more boring than the coverage suggests: there is one thing to check, it takes about ninety seconds, and it is probably your web host’s job rather than yours.

This article is that check, plus the four claims in the coverage that are wrong or overstated. Everything here was verified against the PHP project’s own advisory, the two GitHub security advisories, and WordPress.org on 21 October 2026, and the exploitation status against CISA’s own Known Exploited Vulnerabilities catalogue on 30 October 2026. Security stories move fast, so re-check the dates before you rely on a detail.

What actually happened

PHP is the programming language that runs on the web server behind most websites, including every WordPress site. It is the layer underneath WordPress, not part of WordPress.

The PHP project published an advisory titled “Critical remote code execution vulnerabilities, update now”. Its opening line is the whole story:

“PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities that can allow unauthenticated remote code execution. All PHP users are strongly encouraged to update immediately.”

“Unauthenticated remote code execution” is the worst phrase in security. Unauthenticated means the attacker does not need a password or an account. Remote means they do it over the internet. Code execution means they get to run their own commands on your server. Put together: a stranger runs their program on your machine.

The two flaws are CVE-2026-109618 and CVE-2026-109619 — a CVE number is just a global catalogue entry so everyone can refer to the same bug. Both are rated 9.2 out of 10, “Critical.” The advisory is blunt about who is affected:

“Who is at risk: all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs.”

That last clause matters for WordPress owners. “Before any application code runs” means your WordPress security plugin never gets a turn. The request is handled by PHP itself, underneath everything you installed.

The ninety-second check

The ninety-second check — a painterly illustration conveying this idea from "PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do."

WordPress.org published its own notice the same day, and it is the clearest instruction anyone has given:

“These vulnerabilities are not specific to WordPress and affect any server that hosts a PHP application.”

“No WordPress update is required or planned for these issues.”

Read that second line twice. Updating WordPress does not fix this. If you log in, click “Update,” see a green tick and feel safe, you have not addressed it at all. The fix is a different piece of software on a layer you may never have touched.

Here is the check WordPress.org tells you to run:

  1. Log in to your WordPress dashboard.
  2. Go to Tools → Site Health → Info.
  3. Open the Server section.
  4. Read the PHP version line.

You are looking for 8.5.12, 8.4.27, 8.3.36 or 8.2.35 — or anything higher within those series. If you see one of those, you are patched and you are done.

If you see a lower number, the next step is your host, not you. On managed WordPress hosting — SiteGround, WP Engine, Kinsta, Bluehost and the rest — the host controls the PHP version, and WordPress.org notes that yours “may already be working to update PHP and put web application firewall (WAF) rules in place.” Open a support ticket and ask one question: have you applied the fixes for CVE-2026-109618 and CVE-2026-109619, and which PHP version am I on now? A host that cannot answer that on 22 October is telling you something useful.

Many hosts also let you change the PHP version yourself from the control panel. If yours does and a patched version is offered, take it — but on a staging copy first if you have one, because a PHP jump can break an old plugin.

You may well find the job is already done. I ran this exact check on two sites using SiteGround’s managed PHP service on the evening of 21 October, within hours of the release, and both were already on 8.2.35 — one of the four fixed versions. The panel explained why: the service updates the PHP version automatically when a newer stable one appears. That is not a reason to skip the check, because “managed” means different things at different hosts and on different plans, but it does mean the likely result of your ninety seconds is relief rather than a support ticket.

It is worth reading which version a host like that puts you on, though. 8.2.35 is the fix for the oldest branch still supported, and PHP 8.2 reaches end of life on 31 December 2026. Patched today and current are not the same thing, and an automatic updater that tracks your existing branch will not move you off it when that branch stops receiving fixes.

Four things the coverage is getting wrong

Four things the coverage is getting wrong — a painterly illustration conveying this idea from "PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do."

“70% of websites are vulnerable”

This number is real but it has been bent. It comes from W3Techs, whose page on 21 October 2026 says PHP “is used by 69.3% of all the websites whose server-side programming language we know.”

Two things got lost. It is a share of the sites W3Techs can identify, not of every website in existence. And it measures sites that use PHP — not sites that are vulnerable, and certainly not sites that have been broken into. A patched site is in that 69.3% too.

“Just update WordPress”

Covered above, and worth repeating because it is the single most likely way a reader comes to harm this week. WordPress.org says plainly that no WordPress update is planned for these issues. The thing that needs updating is PHP, and on most hosting that is somebody else’s button.

“AI found it, so AI is now hacking us”

Be careful here. Both official advisories credit four people by username — lcfr-hax, sagitzadik-wiz, tomash-areion and amyb-oai — and neither advisory names any AI model or tool anywhere. The claim that frontier AI models found these bugs comes from the security companies’ own announcements, not from the PHP project’s record of who reported what.

That is not the same as saying no AI was involved. An advisory credits people, not their tooling, so its silence proves nothing either way. It does mean that if you read “AI discovered a flaw in 70% of the web,” you are reading a company’s framing of its own work, and the primary document does not corroborate it.

“It is already being exploited everywhere”

Unsettled when this was written on 21 October, and it has since moved — in one direction. At the time, the security firm watchTowr said it had seen exploitation attempts against its honeypots — decoy servers set up to attract attackers — while CISA, the US government’s cyber agency, said in its own alert that it had not observed exploitation as of publication. Neither CVE was then on CISA’s Known Exploited Vulnerabilities catalogue, the public list of bugs confirmed to be under attack, and Check Point and Greenbone likewise reported none confirmed.

That has changed. CISA added both CVE-2026-109618 and CVE-2026-109619 to the Known Exploited Vulnerabilities catalogue on 26 October 2026. A KEV listing is the agency stating it has reliable evidence a flaw is being used against real systems, and it carries a deadline. Read on 30 October 2026, the catalogue entry for both sets a remediation due date of 29 October for US federal agencies and marks both for mandatory forensic triage — meaning those agencies were required not merely to patch, but to go looking for evidence they had already been hit.

Nothing in the ninety-second check above changes. The fix was always those same four PHP versions and patching was always the advice. What is gone is the argument for putting it off: “it is only theoretical so far” was a defensible position on 22 October and is not one now.

One part of the original claim is still unsupported, though, and it is the word that made it wrong in the first place. “Everywhere” has not been established. A KEV listing means confirmed exploitation somewhere, not mass exploitation, and CISA’s entries for both CVEs still record known ransomware-campaign use as “Unknown”. Confirmed and widespread are different claims, and only the first of them has evidence behind it.

There is one further development that explains why the stakes rose. On 28 October CISA added a Linux kernel flaw, CVE-2026-46300, to the same catalogue, and its entry states the flaw “can be chained with CVE-2026-109618 and CVE-2026-109619 to implant PHP webshells and run commands as root.” Those are the two PHP bugs you just checked for, combined with a flaw in the layer beneath them, turning “a stranger runs their program on your machine” into a stranger owning the whole server. The kernel is your host’s responsibility rather than yours, so your own to-do list is unchanged — but if you wanted a plain answer to whether this is actually serious, that is it.

As of 30 October 2026 no public indicators of compromise had been published, so there is still no reliable way for an ordinary site owner to check whether this specific flaw was used against them. CISA’s forensic-triage requirement lands on federal agencies with incident-response teams, not on someone running one WordPress site. Patch, and do not go hunting for ghosts.

If your site runs PHP 7 or PHP 5, this is a bigger job

If your site runs PHP 7 or PHP 5, this is a bigger job — a painterly illustration conveying this idea from "PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do."

Here is the number worth being alarmed by, and it is not 70%. Of the sites that use PHP, W3Techs recorded 65.2% on PHP 8 — but 27.0% on PHP 7 and 7.7% on PHP 5 on 21 October 2026. That is roughly a third of PHP sites on a branch the PHP project no longer supports.

The advisory is explicit: “PHP 8.1 and older no longer receive updates from the PHP project.” There is no patched PHP 7 release to move to. The team did publish what it calls “minimal source-backports” for PHP 7.4, 8.0 and 8.1, but those are source-code branches for people who compile PHP themselves — not something you click in a hosting panel.

So if Site Health shows PHP 7.4, the instruction “update PHP” quietly means “move to a supported branch,” which can break old plugins and themes and deserves a staging site and an afternoon. Start it this week anyway. And note one more date from the advisory: PHP 8.2 reaches end of life on 31 December 2026, so 8.2.35 is a patch, not a destination.

The other one, from July, that really was exploited

The other one, from July, that really was exploited — a painterly illustration conveying this idea from "PHP Shipped an Emergency Patch. Here Is What a WordPress Owner Actually Has to Do."

There is a second flaw with a confusingly similar name, and conflating them will send you after the wrong fix.

php2shell is this week’s pair, in PHP. wp2shell was a chain of two flaws in WordPress itself — CVE-2026-63030 and CVE-2026-60137 — published on 17 July 2026. The security firm Wiz reported that it was being exploited in the wild, with attackers uploading malicious plugins, attempting to read wp-config, and leaving behind webshells, including one roughly 150KB file disguised as a plugin called “CMSmap.” Wiz attributes the discovery to Searchlight Cyber using an OpenAI model, and names WordPress 7.0.2 as the fixed release.

If you keep WordPress current you are already past it: the maintained releases as of 6 October 2026 are 7.1.3 and 7.0.7. If you have a site that has not been updated since the spring, deal with wp2shell first — not because it is the graver of the two, but because it is the one you can fix from your own dashboard, while php2shell is usually your host’s button to press. Both are now confirmed to have been used against real systems: wp2shell since July, and php2shell since CISA added it to the Known Exploited Vulnerabilities catalogue on 26 October 2026.

What actually changed this week

Strip away the apocalypse framing and the practical shift is narrow but real. The PHP team scheduled its release for 14:00 UTC and had to ship early because details leaked. Defensive firewall rules were reportedly live at some hosts hours before the official announcement. The gap between “a serious bug becomes public” and “the internet is being scanned for it” is now measured in hours.

You cannot win that race by reacting faster, and you should not try. What survives a day like this is the unglamorous state you were already in: a supported PHP version, a host that patches without being asked, WordPress and plugins current, and backups you have actually restored from once. None of that is new advice. This week is just the bill arriving for whether you took it.

Frequently asked questions

Do I need to take my site offline? Almost certainly not. Check your PHP version first. If you are patched, there is nothing to do. If you are not, and your host is unresponsive, the advisory lists interim settings — but they are for server administrators, and the PHP project states that they “reduce exposure to specific attack paths but do not make an installation safe.”

Will Wordfence, Jetpack or my security plugin protect me? Not reliably, and this is the hard part. The advisory describes an exploit that can trigger “before any application code runs” — before WordPress loads, so before your plugin loads. A plugin-level firewall sits too high up to be a dependable answer here. A firewall at the host or CDN level sits in the right place and may help, but it is mitigation, not a fix.

How do I know if I was already hacked? For php2shell, you largely cannot: as of 30 October 2026 no public indicators of compromise had been released, even though CISA now lists both CVEs as being exploited. General signs of a compromised WordPress site still apply: administrator accounts you did not create, plugins you did not install, unexpected changes to files, and your host reporting unusual outbound traffic. If your site sat on an unpatched PHP version and was reachable from the internet after 21 October, the honest position is that you cannot prove it was untouched — so ask your host what its logs show, because it can see more of that traffic than you can.

Is my hosting account itself at risk? The flaws affect the PHP process serving requests. On shared hosting that is a question for your provider about how well customer accounts are isolated from each other — a fair thing to ask in the same support ticket.


📦 Recommended Resources

Some links below are Amazon affiliate links. If you buy through them we earn a small commission at no extra cost to you.

Read the free primary material first — on a story like this the original documents are shorter, clearer and more accurate than the coverage. The PHP project’s security advisory is the authoritative text, including the interim settings for administrators who cannot patch today. WordPress.org’s Critical PHP Security Release notice is the one to send to a non-technical site owner, because it is three paragraphs long and tells them exactly where to look. The two GitHub advisories (GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp) carry the severity scores and the credits. All four are free, and all four were read on 21 October 2026.

The three books below are for the part that is still true next year, when this week’s CVE numbers mean nothing to anyone.

  • Thinking Security: Stopping Next Year’s Hackers by Steven M. Bellovin — the right book for this article, and almost the same argument. Bellovin’s complaint is that security advice hardens into a checklist that people follow long after the threat it answered has changed, which is exactly how a site ends up on PHP 7.4 with a current-looking dashboard. His alternative is to reason about what you are actually defending and against whom. If you only read the chapters on threat models and on “legacy” systems, it will have paid for itself.
  • Building Secure and Reliable Systems by Heather Adkins, Betsy Beyer, Paul Blankinship, Piotr Lewandowski, Ana Oprea and Adam Stubblefield — Google’s companion to the SRE books, and the practical treatment of the dull capability this week actually tested: being able to patch quickly, safely and without drama. The chapters on designing for recovery and on keeping systems updatable are the ones that explain why a host that can roll a PHP version in an afternoon is worth more than any plugin you can install.
  • Threat Modeling: Designing for Security by Adam Shostack — read this one for the layer question. The reason a security plugin is not a dependable answer here is structural: the exploit runs before WordPress loads, so the plugin never gets a turn. Shostack’s method is how you notice that kind of thing on purpose — drawing where your trust boundaries actually sit, rather than assuming the last tool you installed sits at all of them.

✅ Pro tip: put a calendar reminder on your PHP version, not on the news. Once a quarter, open Tools → Site Health → Info → Server, write the PHP version down, and check it against php.net’s supported-versions page. That single habit would have made this week a non-event for you, and it is the only part of this article that still works when the next flaw has a different name. Note one date while you are there: PHP 8.2 reaches end of life on 31 December 2026, so if your host puts you on 8.2.35 today, that is a patch and not a destination.

Newsletter

Tags

Agentic AI Agentic Development AI AI Agents AI Coding Agents Blockchain Bounded Context Browser ChatGPT Plugins Claude Code CLPR Context Engineering Cryptocurrency DePin Developer Tools Distributed Systems DLT Domain-Driven Design Google Search HBAR Hedera Home Networking Internet Internet Performance LLM Machine Learning MCP Model Context Protocol Network Architecture Network Diagnostics Network Security News NLP Postgres PostgreSQL Productivity RAG Routers Saga Pattern SEO Software Architecture software engineering Troubleshooting Twitter Web3

Recent Articles

  • AI Agent Memory: Search and RAG Limits November 6, 2026
  • Plan Locally, Execute in the Cloud: Claude Code’s Own Recommended Workflow November 6, 2026
  • The AI Evaluation Scorer That Never Read a Transcript November 6, 2026
  • What Is a Browser Engine? Blink & V8 Explained November 5, 2026
  • Why Postgres Is Winning: The $1B Acquisition Wave November 5, 2026
  • RENDER Tokenomics Explained: Burn, Mint, Repeat November 5, 2026

Copyright © 2026 · News Pro Theme On Genesis Framework · WordPress · Log in

Content on this site is produced with the assistance of Large Language Models and edited by a human. It is intended for educational purposes — facts may occasionally be incorrect. If you spot an error, please email Larionovdmitri@learninternetgrow.com.

Affiliate Disclosure: This site contains affiliate links to Amazon and other partners. If you purchase through these links, LearnInternetGrow.com may earn a commission at no additional cost to you. We only recommend products we genuinely believe in.

Privacy Policy · Terms of Service