PHP Vulnerability (PHP2Shell): How WordPress Publishers Check and Patch Their Site

The PHP vulnerability behind this week's alerts is PHP2Shell: two critical flaws patched on 21 October 2026, which CISA added to its exploited list on 26 October. This guide shows you how to find your PHP version, confirm your host's patch is actually running and update without breaking plugins. It also has a Japanese summary (php 脆弱性).

Update, 27 October 2026, 6:59 PM: On 26 October, CISA added both PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog, and a researcher confirmed working shells on honeypots. Unit 42 has withdrawn its claim that PHP2Shell was used to break into a European government body. PHP has also shipped Windows rebuilds and confirmed a SimpleXML crash in 8.4.27 and 8.5.12. This update adds a section on how to check that your patch is actually running.

Update, 24 October 2026, 6:58 PM: PHP hadn't put out a new patch or advisory since this post went up. This update added JPCERT/CC's alert with a Japanese summary and patch status from hosts and Linux distributions. It also corrected the release time (14:00 UTC) and removed an FBI/NSA claim we couldn't trace to a primary source.

The PHP vulnerability everyone is searching for is PHP2Shell. It's two critical flaws, CVE-2026-109618 and CVE-2026-109619 (both rated CVSS v4.0 9.2), that let an attacker run code on your server without logging in, before WordPress even loads. CISA now lists both as exploited. The fix is PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, released on 21 October 2026.

The official version list and fix details are in the PHP security advisory of 21 October 2026. Start there if you manage your own server.

Security vendors have covered the CVEs for developers. This guide is for the person who runs the site but not the server. It covers:

  • finding your PHP version in WordPress or your hosting panel
  • checking whether your host or Linux distribution has patched, and what to send your host if it hasn't said
  • confirming the patch is actually running, not just installed
  • updating without breaking plugins
  • locking down a site that publishes on its own

A Japanese summary sits in the Japan section. Everything here is current as of 27 October 2026, 18:59 site time.

Why "php vulnerability" is rising now

Searches spiked because PHP2Shell went from leak to patch to confirmed exploitation in about a week. Governments told people to patch or take sites offline, and on 26 October 2026 CISA formally listed both flaws as exploited. Newest first:

  • 27 October 2026, 18:59 (site time): WriteOut's Google Trends run still shows "php vulnerability" and "php 脆弱性" as Breakout worldwide in Computers & Electronics over 7 days, with "php" up 550%. BleepingComputer published "CISA confirms PHP2Shell vulnerabilities now exploited" and SecurityWeek updated its story.
  • 26 October: CISA added CVE-2026-109618 and CVE-2026-109619 to its KEV catalog and updated its 21 October alert.
    • PHP published Windows rebuilds and confirmed a SimpleXML crash in 8.4.27 and 8.5.12.
    • JPCERT/CC updated JPCERT-AT-2026-0033 to cover CVE-2026-115560.
    • BleepingComputer and SecurityWeek reported working exploits on honeypots.
  • 25 October: Unit 42 retracted its 23 October claim that PHP2Shell was used against a European government agency.
    • CYFIRMA reported a suspected North Korea-linked scanning campaign, which The Hacker News covered.
    • Bitsight put internet-facing systems running PHP or related software at about 37 million.
  • 24 October: Adel Karimi of Perplexity caught working exploits on honeypots. These results were published on 26 October. WriteOut's 13:04 Trends run first flagged both queries as Breakout, with "php" up 500%.
  • 23 October: Several things happened on the same day.
    • PHP disclosed a third flaw, CVE-2026-115560, with no patch yet (php.net notice).
    • CISA said it hadn't seen successful exploitation and released a SIGMA detection rule.
    • The Hacker News reported a failed attempt to install a Mirai botnet variant called "Potassium".
    • Unit 42 described an intrusion at a European government body and linked it to PHP2Shell. It withdrew that link two days later.
  • 22 October: Japan's IPA issued a full security alert and JPCERT/CC published JPCERT-AT-2026-0033. Remi and AlmaLinux shipped patched packages. Hosting provider Sakura went into emergency maintenance. By early 22 October, Cloudflare had counted millions of attempts.
  • 21 October onward: watchTowr and Cloudflare saw attacks in the wild.
    • Government sites in Finland, the Netherlands (including NCSC.nl, MijnOverheid and the Tweede Kamer), Belgium and France went partly or fully offline, some as a precaution (WJLA).
    • UK councils, including Edinburgh and Oxford, and the Met Police were affected too (Insurance Business).
    • An FBI/NSA "take sites offline" warning appears only in secondary reports. We found no primary source for it.
  • 21 October, 14:00 UTC: PHP released the patches. Cloudflare saw tens of thousands of attempts within 45 minutes and hundreds of thousands within 2 hours. The same day, Ubuntu published USN-8948-1, CISA issued an alert, IPA posted a "prepare now" notice and Cloudflare added temporary firewall rules.
  • 20 October: PHP posted an advance notice of a critical release for 14:00 UTC on 21 October. The details had leaked before the planned disclosure, and watchTowr confirmed the bugs were real (BleepingComputer).
  • 17 October: Amazon Threat Intelligence logged the first exploitation attempt on its MadPot honeypots, four days before the patch.

Why Japan is searching "php 脆弱性"

Japan's prime minister and the National Cybersecurity Office (国家サイバー統括室) publicly urged people to patch (nippon.com).

  • IPA and JPCERT/CC both issued alerts, and JPCERT/CC updated its alert on 26 October 2026. It now covers CVE-2026-115560 and says several public proof-of-concept exploits exist and attack attempts are increasing. The vulnerability is also listed in JVN.
  • Sakura went into emergency maintenance, and Japanese providers Xserver and Codmon have announced their own measures.
  • CYFIRMA named Japan among the targets of a suspected North Korea-linked scanning campaign (moderate confidence; these were scans, not confirmed breaches).

If you publish in Japanese, the version table and steps below apply as written.

php 脆弱性(PHP2Shell)日本語まとめ(2026年10月27日時点)

  • PHP2Shell(CVE-2026-109618、CVE-2026-109619)は、ログイン不要でリモートからコードを実行される恐れがある重大な脆弱性です(CVSS v4.0 9.2)。
  • 米国 CISA は10月26日、両 CVE を「悪用が確認された脆弱性(KEV)」カタログに追加しました。ハニーポットでの攻撃成功も報告されています。ただし、10月26日時点で大規模な侵害の公表例はまだありません。
  • 修正版は PHP 8.5.12、8.4.27、8.3.36、8.2.35 です(2026年10月21日公開)。Windows 版は10月26日に再ビルド版(8.5.12-1 など)が公開されました。PHP 8.1 以前には公式の修正版がないため、サポート中のブランチ(8.3 以上を推奨)へ移行してください。
  • 8.4.27 と 8.5.12 では、SimpleXML を使う一部のアプリがクラッシュする不具合が確認されています(セキュリティ修正とは別の変更が原因で、修正版は未リリース)。古いバージョンには戻さず、ホスティング会社に相談してください。
  • WordPress での確認方法:「ツール」→「サイトヘルス」→「情報」タブ →「サーバー」→「PHP バージョン」。WordPress 本体の更新は不要ですが、PHP の更新と PHP-FPM や Apache の再起動が必要です。
  • IPA は10月21日に事前の注意喚起、10月22日に対策情報を公開しました。JPCERT/CC の注意喚起 JPCERT-AT-2026-0033 は10月26日に更新され、CVE-2026-115560 とその緩和策が追加されました。
  • 侵害の兆候:異常に長い、または不正な PHPSESSID。不審な multipart/form-data の POST の直後に出るメモリ上限エラーや HTTP 500。PHP ワーカーの頻繁なクラッシュや再起動。見覚えのないプロセス、外部への通信、新しいファイル。痕跡が見つからなくても、攻撃を受けていないとは言い切れません。
  • 3つ目の脆弱性 CVE-2026-115560(修正版は未公開)は、php.ini、FPM プール設定またはサーバー設定で session.upload_progress.enabled=0 を設定し、すべての PHP ワーカーを再起動することで緩和できます(.user.ini や ini_set() では不可)。

Is your site affected by the PHP vulnerability?

Yes, if your site runs PHP on a version older than the fixed release for its branch. Every self-hosted WordPress site runs on PHP, so every self-hosted WordPress site needs checking.

The way PHP is connected to your web server doesn't protect you. According to the advisories, every PHP setup that serves web requests is at risk: PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed. mod_php is the highest risk, and the confirmed honeypot shells were on mod_php. According to Sysdig, the vulnerable code goes back to PHP 5.4 in 2012.

Both flaws are use-after-free bugs. In plain terms:

  • CVE-2026-109618: when PHP runs out of memory, it leaves request data half built, and the cleanup code then trusts it. It can be triggered while PHP parses a file upload.
  • CVE-2026-109619: memory from one request is freed but then reused by a later request on the same worker.

Early leaks put the severity at 10.0. The PHP Foundation said that was wrong; the official score is CVSS v4.0 9.2. NVD later scored both at CVSS v3.1 9.8. Either way, it's critical.

WordPress itself needs no update. John Blackbourn of the WordPress Security Team said no WordPress update is needed or planned. Updating WordPress doesn't update PHP, and a security plugin can't fix a bug inside PHP. The patch has to come from whoever runs your server.

The problem: another WordPress security story is running at the same time, and it's easy to mix up with this one. Attackers are uploading webshells through CVE-2026-27540 in the WooCommerce Wholesale Lead Capture plugin (Infosecurity Magazine).

The fix: treat it as a separate job. If you use that plugin, update it to version 2.0.3.2 or later. That doesn't patch PHP, and patching PHP doesn't fix the plugin.

How to check your PHP version in WordPress or your hosting panel

The quickest check is inside WordPress: Tools → Site Health → Info → Server. The "PHP version" line shows the full number, such as 8.3.36.

  1. Log in to WordPress as an administrator.
  2. Go to Tools → Site Health, then open the Info tab.
  3. Expand Server and read the PHP version.
  4. Compare it with the table below. The last number must match or be higher: 8.3.36 is safe; 8.3.30 is not. Some servers patch without changing the version number (see the section on confirming the patch below).

Not on WordPress, or locked out of admin? Look in your hosting control panel. In cPanel, it's usually under MultiPHP Manager or Select PHP Version. In Plesk, check the PHP settings for your domain, and see Plesk's knowledge base article on PHP2Shell for the PHP that ships with Plesk.

The problem: your developer runs php -v on the server and reports a safe number. That command shows the command-line PHP, which can be a different build from the PHP-FPM or Apache PHP actually serving your site.

The fix: trust Site Health or a phpinfo() page loaded through the website, because both show the PHP that serves real requests.

The problem: hosting panels often show only the branch ("PHP 8.3"), not the patch level. On shared hosting you pick the branch, but your host installs the patches.

The fix: check your host's status page or blog first. SiteGround, for example, published a notice on what it did. If your host hasn't said anything, send support this:

"Is the PHP running on my account patched for CVE-2026-109618 and CVE-2026-109619? Please confirm the exact version (8.5.12, 8.4.27, 8.3.36, 8.2.35 or later) or the distribution package and advisory you applied, the date, and that PHP-FPM or Apache was restarted afterwards. Please also confirm session.upload_progress.enabled=0 is set for CVE-2026-115560."

Which PHP versions fix PHP2Shell?

Four releases fix both flaws: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. There is no official numbered release with the fix for 8.1 or older.

Your branchSafe versionStatus as of 27 October 2026
PHP 8.58.5.12 or later (Windows: 8.5.12-1)Supported; SimpleXML crash confirmed in 8.5.12, fix not yet released
PHP 8.48.4.27 or later (Windows: 8.4.27-1)Supported; SimpleXML crash confirmed in 8.4.27, fix not yet released
PHP 8.38.3.36 or later (Windows: 8.3.36-1)Supported
PHP 8.28.2.35 or later (release announcement; Windows: 8.2.35-1)End of life on 31 December 2026; plan your move to 8.3 or newer
PHP 7.4, 8.0, 8.1No official releaseThe PHP security team published minimal source patches only, with no tarballs or Windows builds. Use distribution or long-term-support vendor packages, or upgrade.
PHP 5.4 to 7.3None upstreamNo upstream fix of any kind. Some long-term-support vendors, such as TuxCare, sell patched builds for older branches.

Release notes for each version are in the PHP news archive. Developers can read the technical write-ups in PHP's GitHub advisories for CVE-2026-109618 and CVE-2026-109619.

The problem: after updating to 8.4.27 or 8.5.12, some apps that use SimpleXML crash (php-src #24488). PHP confirmed this on 26 October 2026. It comes from a separate garbage-collector fix, not from the security patches. The fix is merged in the source code but not yet released, according to Tenable's FAQ.

The fix: don't roll back to an unpatched version. Test anything that reads XML (feed importers, sitemap plugins, product imports). If one of them crashes, ask your host to run your site on another patched branch your plugins support, such as 8.3.36, or pause that plugin until the next release.

The problem: you run PHP on Windows and the version number didn't change, so you assume the 26 October rebuild doesn't apply to you.

The fix: the 26 October rebuilds (8.5.12-1, 8.4.27-1, 8.3.36-1, 8.2.35-1) bundle Brotli 1.2.1, which fixes CVE-2026-111497. That bug can only be reached through cURL with automatic decompression turned on. Install the rebuild anyway; it costs little.

Has your host or Linux distribution patched PHP yet?

Most major Linux distributions and large hosts shipped fixes between 21 and 22 October 2026. Some hosting plans were still waiting on vendor packages at that point. If your site runs on a VPS or dedicated server, your developer installs the packages. On shared hosting, your host does.

SourceStatusDate
UbuntuPatched packages, USN-8948-121 October 2026
Remi repository (RHEL, Rocky, Alma)Patched packages22 October 2026
AlmaLinuxPatched packages22 October 2026
RHEL 9, php:8.4 moduleListed as "Affected", according to one Japanese vendor recap on note.com; not confirmed with Red HatAs of 24 October 2026
PantheonPatched PHP 8.2 to 8.521 to 22 October 2026
Rocket.netPatched PHP 5.2 to 8.5, without changing the version number21 to 22 October 2026
GoDaddyManaged WordPress patched. Web Hosting and Windows Hosting were waiting on vendor packages. VPS customers must update PHP themselves.21 to 22 October 2026
Sakura (Japan)Emergency maintenance22 October 2026
SiteGroundPublished noticeOctober 2026

Host statuses move fast. If yours was "waiting" on 22 October, ask again now.

How to confirm the PHP2Shell patch is actually running

Your site is only safe once the PHP serving your pages runs the fixed code. A patched package on disk does nothing until PHP-FPM, Apache or any other long-running PHP workers restart. Check these with your host or developer:

  1. Read the version from the web, not the command line. Use Site Health or a phpinfo() page. php -v can show a different build.
  2. Same number, new build. Distribution packages and some hosts, such as Rocket.net, apply the fix without changing the version number. On those, check the package changelog or distribution advisory for both CVE numbers. Alternatively, check the build date in phpinfo(): 21 October 2026 or later means the fix is in.
  3. Look for old code still in memory. On Linux, if a php-fpm process's executable path (for example ls -l /proc/PID/exe) ends in "(deleted)", that worker is still running the old binary. Restart it.
  4. Rebuild containers. A running Docker container keeps its old PHP. Rebuild the image with docker build --pull and redeploy.
  5. Remove any phpinfo() page you created for the check, because it exposes your server configuration.

A step-by-step version for developers is in this dev.to patch check guide.

How to update PHP safely without breaking plugins

A patch within your current branch (say, 8.3.x to 8.3.36) is low risk. Patch releases fix bugs and security holes; they don't change how PHP behaves. The SimpleXML crash in 8.4.27 and 8.5.12 is the exception, so test for it. Jumping branches (7.4 to 8.3) is where plugins break. Either way, go in this order:

  1. Back up files and database. Use your host's backup tool or your backup plugin. Download a copy you can still reach if the site goes down.
  2. Patch within your branch first. On managed or shared hosting, this is the host's job; get written confirmation using the message above. On a VPS, your developer updates the PHP packages and restarts PHP-FPM or the web server.
  3. Recheck Site Health. Confirm the new version number (or a 21 October or later build date) appears, not just the branch.
  4. Test what earns you money. Load the home page, submit a contact form, upload an image to the media library, run a test checkout if you sell anything and open your affiliate links. Also run anything that reads XML feeds or sitemaps.
  5. Clear caches. Clear the plugin cache, server cache and CDN, so you're testing the live site.

What if you're on PHP 7.4, 8.0 or 8.1?

You need to move to a supported branch, ideally 8.3 or 8.4. PHP's patches for 7.4, 8.0 and 8.1 are source code only, with no tarballs or Windows builds. Most hosts and site owners can't realistically compile and run them. Ask your host whether it has applied a backport from its distribution or a long-term-support vendor. Searches for "php 7.4 vulnerability" are rising for this reason. On 7.3 or older there's no upstream fix at all.

  1. Update WordPress core, every plugin and your theme before you switch PHP. Old plugin versions cause most PHP 8 breakages.
  2. Delete plugins you no longer use rather than updating them.
  3. Switch PHP on a staging copy first, if your host offers one. Click through the site and watch for white screens or error messages.
  4. If a plugin you can't do without breaks and has no update, replace it. As of 27 October 2026, CISA lists both flaws as exploited. Keeping one plugin isn't worth staying on an unpatched branch.
  5. Switch the live site, then repeat the tests from the section above.

Can't patch yet? Temporary PHP2Shell mitigations

PHP says: "There are no complete mitigations, updating is the only safe choice." The settings below lower the risk until you can patch, and Datadog describes them as partial. They're for your host or developer, not for a WordPress settings screen.

  • memory_limit=-1, set with php_admin_value so applications can't override it. Combine it with request limits at the front end and container memory limits.
  • A low post_max_size: 8M, or 32M if your site needs uploads.
  • session.upload_progress.enabled=0 in php.ini, the FPM pool or the server config (not .user.ini or ini_set()), then restart all PHP workers.
  • On PHP 8.5 only: fatal_error_backtraces=0.
  • Request size and count limits at the web server or proxy, plus container or cgroup memory limits. The advisories say not to use RLIMIT_AS or RLIMIT_DATA.

The problem: you think a firewall covers you. Cloudflare's temporary rules help, and Wordfence says its firewall blocked more than 74,000 attempts. But Bitsight and Patchstack are clear that a WAF doesn't fully protect you.

The fix: treat the WAF as a speed bump and keep pushing for the patched version.

The problem: you switch on a WordPress maintenance-mode plugin and assume the site is paused. The exploit runs before any application code. Your plugin is application code, so PHP still processes the attack.

The fix: "pause the site" has to happen at server or host level. Ask your host to stop PHP serving requests or take the site off the public internet. CISA, IPA and Japan's National Cybersecurity Office all recommend this if you can't patch.

How to protect a site that publishes automatically

Auto-publishing sites carry extra exposure: stored API keys, application passwords and scheduled jobs that keep running while you're patching. With an RCE flaw, an attacker who gets a shell can read your wp-config.php and every credential your pipeline uses. The 24 October honeypot results show attackers getting working shells on a vulnerable setup, so treat this as a real risk.

The problem: scheduled posts and publishing integrations keep calling your site during the patch window.

The fix: pause scheduled publishing and external integrations until Site Health shows a patched version and the workers have restarted. Resume after testing.

The problem: your site ran an unpatched PHP version after 17 October, when the first attempts were seen.

The fix: check for compromise as well as patching. CISA's directive for US federal agencies asks them to do the same. Ask your host or developer to check logs back to 17 October for the signs JPCERT/CC lists:

  • unusually long or malformed PHPSESSID cookies
  • suspicious multipart/form-data POSTs followed by memory-limit errors or HTTP 500s
  • PHP workers crashing or restarting often
  • unexpected processes, outbound connections or new files

Finding none of these doesn't prove the site wasn't attacked. After patching:

  • Rotate WordPress application passwords, API keys for any publishing tool, your database password and your admin passwords.
  • Check Users for admin accounts you don't recognise.
  • Ask your host to scan for recently changed or unknown files.

The problem: nobody owns the patch because the site "runs itself".

The fix: name one person on your desk to confirm the PHP version and worker restart in the week of 27 October 2026. They should check again when the SimpleXML fix and CVE-2026-115560's fix ship, and again when 8.2 reaches end of life on 31 December 2026.

What is the third PHP flaw, CVE-2026-115560?

CVE-2026-115560 is a remote code execution risk in session upload progress. PHP disclosed it in an informational advisory on 23 October 2026 and called it an "unlikely RCE vector". It has no patch yet, and the 21 October releases don't fix it. JPCERT/CC added it and its mitigation to JPCERT-AT-2026-0033 on 26 October 2026. As of 27 October 2026:

  • No CVSS score or list of affected versions has been published.
  • No exploitation has been reported.
  • The fix is due in the next regular bugfix release, which has no date yet. The next dated PHP event is 8.6.0 RC5 on 5 November. That's a test release, not something to run in production.

It only matters with an unusual setup: session.serialize_handler set to php_binary or php_serialize, then switched to php with ini_set() before session_start(), with upload progress still enabled.

  • Mitigation: set session.upload_progress.enabled=0 in php.ini, the FPM pool or the server config, then restart all PHP workers. Setting it in .user.ini or with ini_set() doesn't count. This is what "php-fpm restart upload_progress" searches are about; serversideup's write-up walks through it.
  • Already done it? Sites that set this for CVE-2026-109619 are covered.
  • Not a substitute for patching: the setting doesn't protect against CVE-2026-109618, so you still need 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

Is the PHP vulnerability being exploited?

Yes. On 26 October 2026, CISA added CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalog, and a researcher confirmed working shells on honeypots. Success depends on the setup, though, and most attempts seen so far failed. As of 26 October, SC World reported no public reports of successful exploitation at scale.

  • Working shells (24 October): Adel Karimi of Perplexity ran PHP 8.4.26 on Apache mod_php with a single worker.
    • The honeypots caught 35 shells across 3 machines, from 2 IP addresses. The attackers used a four-step request chain (exhaust memory, leak memory, run a shell command) that closely matches a public proof of concept.
    • No second-stage payload was seen.
    • Karimi warned that the setup was deliberately favourable to the exploit, so it doesn't show how reliable the exploit is elsewhere.
    • Expel's Marcus Hutchins called it the "highest quality confirmation" so far (BleepingComputer, SecurityWeek, 26 October).
  • CISA's deadline: under BOD 26-04, US federal civilian agencies must fix both flaws by 29 October 2026 and check whether their systems were compromised. That due date comes from BleepingComputer and Tenable; CISA's 26 October alert page doesn't show it.
  • Retracted intrusion claim: on 25 October, Unit 42 withdrew its 23 October claim linking an attack on a European government agency to PHP2Shell. It now says it "cannot confirm" the attackers got in through these CVEs. Coverage before 25 October that cites that breach is out of date.
  • State-linked scanning: CYFIRMA reported a suspected Lazarus-linked campaign in which 21 compromised nodes scanned 216 unpatched or partly mitigated hosts in the US, Japan, South Korea, the EU and elsewhere. The targets were in government, finance, logistics, aviation and manufacturing. CYFIRMA gives this moderate confidence, and these were scans, not confirmed breaches (The Hacker News, 25 October).
  • Lab results: Wordfence got code execution only in a specially configured lab; a standard PHP build just crashed. VulnCheck chained the two bugs to defeat ASLR (a memory-randomisation protection) and run code on x86-64 systems with production settings.
  • Attack volume: Cloudflare counted tens of thousands of attempts within 45 minutes of disclosure and "millions" by 25 October. JPCERT/CC said on 26 October that several public proof-of-concept exploits exist and attempts are increasing.

How many sites are at risk depends on who you ask. All of these are vendor counts of systems, services or instances, not unique websites, so don't quote any of them as a site count:

SourceFigureDate
W3Techs (cited in October 2026 coverage)PHP runs about 70% of websites whose server-side language is knownOctober 2026
BitsightAbout 37 million internet-facing systems running PHP or related software25 October 2026
CensysMore than 34.4 million PHP services assessed as vulnerable23 October 2026
Unit 42's Cortex Xpanse22.6 million potentially exposed instances23 October 2026

The Hacker News also reported that the UK government confirmed 32 digital services were unavailable and 4 partly unavailable, and that the NCSC sent about 50,000 warnings. We found those UK figures only in that report.

From the desk: When WriteOut's run fetched Trends at 13:04 on 24 October 2026, "php vulnerability" and "php 脆弱性" both showed as Breakout in the same 7-day window, with "php" at +500%. Three days later, on 27 October, both were still Breakout and "php" had climbed to +550%. The question people were searching had changed, though. On 24 October it was "am I affected?" By 27 October, with CISA listing the flaws as exploited, it was "did my patch actually take?" That's why this update adds a verification section to the same URL instead of starting a second post. [ANMOL: add whether you checked or patched KyunTrend's PHP version and how long it took.]

How WriteOut fixes it

The problem: PHP2Shell leaked on 20 October 2026, and by 23 October the first page of results was full. A week later the story is still moving, with CISA's listing, a retracted breach claim and a regression. If your desk covers a story like this late, or never updates it, you're rewriting what already ranks.

The fix: WriteOut checks rising Google searches in your niche every few hours. It drafts the post in your site's voice and publishes it to WordPress, a static site or any CMS only after you approve it. Nothing goes live on autopilot, so you stay in control during a week like this one. Built for bloggers and news portals who need to be first.

Learn more →

The short version

  • PHP2Shell is two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, rated CVSS v4.0 9.2. PHP patched them on 21 October 2026 at 14:00 UTC.
  • The safe versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Check yours under Tools → Site Health → Info → Server, then confirm PHP-FPM or Apache has restarted. WordPress itself needs no update.
  • CISA added both flaws to its Known Exploited Vulnerabilities catalog on 26 October 2026 after honeypots caught working shells. Unit 42 has retracted its government breach claim, and there were no public reports of mass successful exploitation as of 26 October.
  • 8.4.27 and 8.5.12 can crash some SimpleXML apps. Don't roll back. Ask your host about another patched branch until the fix ships.
  • On 8.1 or older there's no official fixed release. Move to a supported branch after updating plugins and themes.
  • A WAF or maintenance-mode plugin won't stop this exploit. For CVE-2026-115560, which is still unpatched, set session.upload_progress.enabled=0 at server level and restart the workers.

Sources

  1. PHP security advisory, 21 October 2026 · The PHP Group
  2. CISA Adds Two Known Exploited Vulnerabilities to Catalog, 26 October 2026 · CISA
  3. Critical Vulnerabilities in PHP Require Immediate Patching (updated 26 October 2026) · CISA
  4. Advisory on CVE-2026-115560, 23 October 2026 · The PHP Group
  5. Windows Brotli rebuilds, 26 October 2026 · The PHP Group
  6. Advance release notice, 20 October 2026 · The PHP Group
  7. PHP 8.2.35 released · The PHP Foundation
  8. GHSA-w8hw-w9fx-j79w (CVE-2026-109618) · php-src on GitHub
  9. GHSA-6wmf-4rv5-p3rp (CVE-2026-109619) · php-src on GitHub
  10. JPCERT-AT-2026-0033 (updated 26 October 2026) · JPCERT/CC
  11. JVNVU#99905564 · JVN
  12. PHP security alert, 22 October 2026 · IPA (Japan)
  13. PHP pre-alert, 21 October 2026 · IPA (Japan)
  14. Security Advisory 2026-018 · CERT-EU
  15. AL26-026: Critical vulnerabilities impacting PHP · Canadian Centre for Cyber Security
  16. PHP2Shell in PHP shipped with Plesk · Plesk
  17. Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure · AWS
  18. CVE-2026-109618 and CVE-2026-109619 threat brief · Unit 42, Palo Alto Networks
  19. PHP2Shell FAQ · Tenable
  20. PHP2Shell vulnerabilities · VulnCheck
  21. PHP2Shell: critical vulnerabilities in PHP · Datadog Security Labs
  22. PHP CVE-2026-109618 FAQ · watchTowr
  23. PHP major vulnerability alert · Patchstack
  24. CISA confirms PHP2Shell vulnerabilities now exploited · BleepingComputer
  25. PHP2Shell security flaws now successfully exploited in the wild · BleepingComputer
  26. PHP2Shell exploitation moves from probes to working shells · SecurityWeek
  27. PHP2Shell exploitation confirmed, but mass attacks remain elusive · SC World
  28. PHP2Shell exploitation and North Korea-linked scanning · The Hacker News
  29. PHP2Shell exploit attempts hit millions · The Hacker News
  30. PHP warns of another unpatched flaw · The Hacker News
  31. How to check your server has the PHP2Shell patch · dev.to
  32. PHP CVE-2026-115560 and session upload progress · serversideup
  33. Critical PHP vulnerabilities, October 2026 · SiteGround
  34. UK councils and Met Police among sites pulled offline after NCSC alert · Insurance Business
  35. Critical PHP flaws put millions of websites at risk as governments pull sites offline · WJLA
  36. WooCommerce Wholesale Lead Capture flaw exploited · Infosecurity Magazine
  37. Japan urges PHP patching · nippon.com
  38. PHP2Shell recap (Japanese) · note.com

Frequently asked questions

What is the PHP vulnerability PHP2Shell?

PHP2Shell is the name for two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Both are use-after-free bugs rated CVSS v4.0 9.2. An attacker needs no login, and the exploit runs before any application code. PHP released fixes at 14:00 UTC on 21 October 2026 in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. CISA added both flaws to its exploited list on 26 October 2026.

How do I check my PHP version in WordPress?

In WordPress, go to Tools, then Site Health, open the Info tab and expand Server. The PHP version line shows the full number, such as 8.3.36. Don't rely on php -v, which shows the command-line PHP. Some hosts and Linux distributions patch without changing the version number. On those, a phpinfo() build date of 21 October 2026 or later means the PHP fix is in.

Does WordPress need an update for the PHP vulnerability?

No. John Blackbourn of the WordPress Security Team said no WordPress update is needed or planned for PHP2Shell. The PHP vulnerability is in PHP itself, so updating WordPress or installing a security plugin cannot fix it. Every self-hosted WordPress site, including on shared hosting, needs its host or developer to install a patched PHP version or distribution package and then restart PHP workers.

Is the PHP2Shell vulnerability being exploited?

Yes. CISA added both PHP2Shell CVEs to its Known Exploited Vulnerabilities catalog on 26 October 2026, after a researcher's honeypots caught 35 working shells on a deliberately favourable mod_php setup. Most attempts seen so far failed, and SC World found no public reports of mass successful exploitation as of 26 October. Unit 42 retracted its government breach claim on 25 October 2026.

What should I do if my site runs PHP 7.4 or 8.1?

A site on PHP 7.4, 8.0 or 8.1 gets no official fixed release, only minimal source patches without tarballs or Windows builds. Ask your host about backports from your distribution or a long-term-support vendor. Otherwise, update WordPress core, plugins and theme, test on staging, then switch to PHP 8.3 or 8.4. PHP 5.4 to 7.3 gets no upstream fix at all.

What is CVE-2026-115560?

CVE-2026-115560 is a third PHP remote code execution flaw, in session upload progress. PHP disclosed it on 23 October 2026, and it still had no patch, CVSS score or reported exploitation as of 27 October 2026. JPCERT/CC added it to its alert on 26 October. The mitigation is setting session.upload_progress.enabled=0 at server level and restarting all PHP workers. You still need the PHP2Shell patch.

Sources

  1. CISA Adds Two Known Exploited Vulnerabilities to Catalog · CISA
  2. PHP security advisory, 21 October 2026 · The PHP Group
  3. Critical Vulnerabilities in PHP Require Immediate Patching · CISA
  4. JPCERT-AT-2026-0033 · JPCERT/CC
  5. PHP2Shell security flaws now successfully exploited in the wild · BleepingComputer
  6. PHP2Shell FAQ: CVE-2026-109618 and CVE-2026-109619 · Tenable
  7. PHP2Shell exploitation confirmed, but mass attacks remain elusive · SC World

Keep reading.

All posts →

WriteOut is in early access.

Leave your email and the site you'd use it on. We're letting people in one site at a time.