PHP security and the WordPress plugin's PHP requirement
PHP2Shell and your WordPress site: what to update, and why our plugin asks for PHP 8.1
On 21 October 2026, PHP shipped fixes for two critical flaws that let an attacker run commands on a web server with a single request. If your site runs WordPress, the fix is a PHP update at your host, not a plugin update. Here is what happened, which PHP versions are safe today, and where the Lionrapid plugin's PHP 8.1 requirement fits in.
Most WordPress owners never think about PHP. It is the language WordPress is written in, and it runs on your host's server underneath everything else: your theme, your plugins, your pages. You pick a host, the host picks a PHP version, and the site works.
In October that layer had a bad week. Two flaws in PHP itself, nicknamed PHP2Shell, let an attacker send one crafted request to any PHP page and run commands on the server. No login was needed, and the attack lands before WordPress or any plugin has run a single line. A firewall plugin cannot stop it. A security plugin cannot stop it. The fix lives one floor down, in PHP.
The good news is that the fix is ordinary: move your site to a current PHP release. Many hosts let you change the PHP version in their control panel; if yours does not, ask them. The rest of this post explains what was found, why older PHP versions stay exposed, why our WordPress plugin asks for PHP 8.1 or newer, and the short checklist we would run on our own site this week.
Lionrapid itself does not run on PHP. The PHP in this story is the one on your WordPress host, where our WordPress translation plugin runs beside your other plugins.
What happened in October
On 21 October 2026 the PHP project released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 with a security advisory titled "Critical remote code execution vulnerabilities, update now". The releases fix two flaws, both rated critical at 9.2 on the CVSS 4.0 scale:
- CVE-2026-109618. When PHP runs out of memory while it is still reading an incoming request, its cleanup can treat half-built data as valid. A crafted request can turn that into running commands on the server. Datadog's analysis puts it plainly: PHP processes the malicious request before any application code runs.
- CVE-2026-109619. Internal state from one request can survive into the next request handled by the same PHP worker, after its memory has been freed. One way in goes through session upload progress, a feature that has been on by default since PHP 5.4.
Google's response team lists every PHP version from 5.4 through 8.5.11 as affected. The UK's National Cyber Security Centre told organisations to update to the latest PHP and to take a system offline if it cannot be fixed or mitigated.
This is not a theoretical bug. Technical details leaked publicly hours before the planned release. watchTowr reports exploitation in the wild since 21 October, and says the US agency CISA added CVE-2026-109618 to its catalogue of known exploited vulnerabilities on 26 October. Attackers scan for PHP servers in bulk, and a WordPress site is a PHP server, whatever it sells or says.
PHP also published stopgap settings for servers that cannot update at once: switching off session upload progress, and memory limits set by the administrator. Every analysis we read agrees on the same point. They reduce exposure, they do not close it. An updated PHP does.
Why an older PHP stays open
PHP looks after each release line for a fixed time: about two years of full support, then two more years of security fixes only, then nothing. When a line reaches its end of life, the next critical flaw simply does not get an official fix for it. October showed what that means in practice.
These are the lines php.net supports today, with the date each one stops receiving security fixes:
- PHP 8.5: security fixes until 31 December 2029.
- PHP 8.4: until 31 December 2028.
- PHP 8.3: until 31 December 2027.
- PHP 8.2: until 31 December 2026. It got the October fix, but it has weeks left, not years.
And these are the lines that have reached end of life:
- PHP 8.1: ended 31 December 2025. Its last official release is 8.1.34.
- PHP 8.0: ended 26 November 2023.
- PHP 7.4: ended 28 November 2022.
For PHP2Shell there is no official release for 8.1 or anything older. The PHP security team did publish minimal source patches for 7.4, 8.0 and 8.1, but a source patch is not something a site owner installs. Someone has to build it into PHP and ship it, usually a Linux distribution with long-term support or your host. If they did, your version number may not even change, so the number alone cannot tell you whether you are protected. Only your host can.
The scale is not small. On 21 October, VirusTotal counted about 758,000 internet-facing hosts running PHP lines from 5.4 to 8.1, all past end of life, against about 272,000 on the supported lines from 8.2 to 8.5. That is nearly three servers on an old line for every one on a current line.
WordPress says the same thing in its own words. Its requirements page recommends PHP 8.3 or newer. WordPress still runs on PHP 7.4 and up for older environments, but the page warns that those versions have reached their end of life and may expose your site to security vulnerabilities. Running is not the same as being safe.
Why our plugin asks for PHP 8.1
The Lionrapid Translation plugin needs PHP 8.1 or newer (the plugin documentation lists the requirements). The reason is in the code itself. The plugin is written in modern PHP and leans on readonly properties, a language feature that arrived in PHP 8.1. A readonly value is set once and can never change afterwards. For a plugin that sits in the middle of every page your site serves, that is exactly what you want: the settings it reads at the start of a request stay the settings it uses until the end, whatever else runs on the site.
PHP 8.0 and older simply cannot read that code, so we do not pretend they can. The plugin says PHP 8.1 everywhere WordPress looks:
- In its header and readme. WordPress reads the line "Requires PHP: 8.1" and will not activate the plugin on an older PHP. It shows its own message instead of a broken page.
- In a check that runs before anything else. If the plugin is already on a site whose PHP is older, it loads nothing at all and says so on the Plugins screen: "Lionrapid Translation needs PHP 8.1 or newer and is not running. Ask your host to update PHP."
- In every change we make. Each change to the plugin's code is checked against PHP 8.1 before it can be merged, so a feature from a newer PHP cannot slip in unnoticed.
Two honest notes go with the requirement.
The floor is where the plugin works, not where we would leave a site. PHP 8.1 reached its end of life on 31 December 2025 and received no official PHP2Shell release. The plugin will run there, but the server under it is the weak point. For security, run a supported PHP line. Today that means PHP 8.3 at the least, and PHP 8.4 or 8.5 once their next point releases are out (more on that in the checklist below).
No plugin can fix a flaw in PHP, ours included. PHP2Shell is triggered while PHP is still reading a request, before WordPress or any plugin runs. What a plugin can do is stay out of the way of the fix: run on current PHP, and not hold your site back on an old line. That is the job our requirement does.
What to do this week (if you haven't already)
The whole fix fits in five steps. None of them touches your content, and an afternoon is plenty.
- Find your PHP version. In WordPress, open Tools → Site Health → Info and expand Server. The PHP version is listed there. Your host's control panel shows it too.
- Pick the version to move to. On 21 October PHP's fixed releases were 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Two of them, 8.4.27 and 8.5.12, have a known crash that the WordPress hosting handbook describes, fixed upstream for the next point releases, 8.4.28 and 8.5.13. Until those ship, PHP 8.3.36 is the safe choice: it has both security fixes and not the crash. Do not go back to an older release to dodge the crash: every earlier version carries the flaws.
- Back up, then switch. Take a backup first, whether that is your host's snapshot or your usual backup plugin. Then change the PHP version in your host's control panel, or ask your host to do it.
- Check the site. Open a few pages, log in to the dashboard, and look at Site Health again. If something breaks, it is usually an old plugin or theme that has not kept up with PHP. Update it, replace it, or switch PHP back while you sort it out, and talk to your host.
- Stay current. Check the PHP version once a quarter, the same way you check plugin updates. PHP 8.2 reaches its end of life on 31 December 2026, so a site on 8.2 has one more move to make soon.
If your host cannot update PHP quickly, ask what it has done in the meantime. The stopgap settings from PHP's advisory are the host's to apply: they reduce the risk but do not remove it. A host that cannot answer that question is worth a second look.
And if the Lionrapid plugin is on your site, moving PHP up is all it asks of you: every version this checklist recommends meets its PHP 8.1 requirement.