---
title: "Is WordPress Safe After PHP2shell? Patch PHP, Then Decide on React"
description: "PHP2shell was exploited in 2026. Learn which PHP releases fix it, how to assess WordPress, and when a React/Next.js migration makes business sense."
canonical: https://itsupportintokyo.com/en/blog/wordpress-php-security-2026-react-nextjs-migration
language: en-US
published: 2026-11-16T09:00:00.000Z
modified: 2026-11-16T09:00:00.000Z
author: "IT Support in Tokyo Team"
keywords: "is WordPress safe 2026, PHP security vulnerability 2026, WordPress PHP security, migrate WordPress to React, WordPress to Next.js migration, secure website migration Japan"
image: https://itsupportintokyo.com/article-assets/wordpress-php-migration/hero-security-review.webp
translations: ["https://itsupportintokyo.com/ja/blog/wordpress-php-security-2026-react-nextjs-migration","https://itsupportintokyo.com/th/blog/wordpress-php-security-2026-react-nextjs-migration"]
---

# Is WordPress Safe After PHP2shell? Patch PHP, Then Decide on React

> PHP2shell was exploited in 2026. Learn which PHP releases fix it, how to assess WordPress, and when a React/Next.js migration makes business sense.

**WordPress and PHP can be run securely. The harder question is whether your site can keep up with the work required.** A major PHP security release in October 2026 is a useful reminder: the safety of a business website depends on its runtime, plugins, hosting, access controls and update process—not the name of its framework alone.

If your website has grown into a customer portal, multilingual lead engine or product interface, a carefully planned React and Next.js migration may reduce the WordPress-specific surface you must maintain. It must also preserve your content, search visibility and editorial workflow. This guide shows how we make that decision with clients.

Need to identify the PHP version and plugin risks on your own site? [Ask IT Support in Tokyo for a WordPress/PHP review](/en/contact).

Reviewed November 16, 2026. The images in this article are editorial illustrations and conceptual diagrams, not screenshots of an attack or a customer system.

## PHP2shell: what happened in October 2026?

On October 21, 2026, the [PHP project disclosed](https://www.php.net/archive/2026.php#2026-10-21-5) two critical vulnerabilities—CVE-2026-109618 and CVE-2026-109619—and released fixes in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. [Japan's IPA](https://www.ipa.go.jp/security/security-alert/2026/alert20261022.html) refers to the pair as **PHP2shell** and reports that both entered CISA's Known Exploited Vulnerabilities catalog on October 26. The advisories concern the PHP runtime. [WordPress said](https://wordpress.org/news/2026/10/critical-php-security-release/) this was **not a WordPress-specific flaw** and did not require a WordPress core update for these issues.

Known exploitation does not prove that every WordPress site was hacked. **Patch first:** check the PHP version actually serving your site, coordinate a fixed supported release or verified vendor backport with your host, test compatibility and backups, then investigate logs and indicators if you suspect misuse. Do not assume that updating WordPress alone patches the runtime underneath.

![Diagram showing how the PHP runtime, WordPress core, themes, plugins and hosting controls each affect site security](/article-assets/wordpress-php-migration/wordpress-risk-path-en.svg)

Conceptual risk map: an update to one layer does not automatically update the others. On a phone, swipe horizontally to read the diagram.

## Is WordPress safe for a business website?

Yes, when it is actively maintained and fits the job. WordPress remains a practical choice for many editorial and company sites. The risk increases when a site relies on numerous plugins, abandoned themes, privileged accounts, unpatched PHP or a host with weak backups and monitoring. Each component and integration adds a maintenance obligation.

Before proposing a rebuild, we inventory the live system: PHP version, WordPress core, installed and inactive plugins, theme code, users and roles, forms, payment connections, backups, firewall rules, exposed files, logs and update ownership. We also identify which features bring revenue and which are only historical baggage.

![Editorial photograph of a development team reviewing website dependencies and security maintenance on a desktop screen](/article-assets/wordpress-php-migration/dependency-inventory.webp)

Editorial illustration of a dependency review; the screen does not document a specific breach.

## Would moving to React make the site secure?

**React by itself is a user-interface library, not a security upgrade.** Replacing a WordPress theme with a React frontend while keeping the same vulnerable server and plugins does not remove those risks. A full migration can remove the public WordPress/PHP runtime and unwanted plugins, but the new application introduces its own dependencies, APIs, authentication, deployment pipeline and access rules.

For a search-driven company website, we usually evaluate Next.js rather than a browser-only React application. It can render important page content and metadata on the server, provide stable localized routes and support a clear split between public pages and protected application features. The architecture must still be tested for authorization, input handling, dependency updates, backups and incident response. A December 2025 React Server Components advisory is a reminder that modern stacks need prompt patching too.

## When should you keep WordPress—and when is migration worth it?

Keep WordPress if editors depend on it, the site performs well, its plugins are supported, updates are owned and your host can demonstrate reliable backup and recovery. A focused hardening project may solve the real problem faster than a rebuild.

Consider migration when plugin conflicts repeatedly block changes, a theme limits the experience, important features belong in a custom app, bilingual content is difficult to govern, or maintenance costs keep growing. The case is strongest when a redesign, new business workflow and security cleanup can be delivered together.

![Editorial photograph of business leaders and developers planning a secure website migration at a meeting table](/article-assets/wordpress-php-migration/migration-planning.webp)

Editorial illustration of a planning workshop; business requirements and editorial needs shape the architecture.

## Our migration flow: protect the business before replacing the stack

![Five-stage WordPress to Next.js migration diagram covering audit, architecture, build, launch and ongoing operations](/article-assets/wordpress-php-migration/migration-flow-en.svg)

Conceptual delivery flow. Each stage has an explicit review before the next one begins. On a phone, swipe horizontally to read the diagram.

- **Audit the current site.** Inventory URLs, content, forms, plugins, PHP versions, Search Console data, traffic, backlinks, conversions and known vulnerabilities.
- **Choose the architecture.** Keep WordPress, use it as a headless CMS, or replace it. Define who edits content and how data moves.
- **Build and test.** Create server-rendered pages, localized metadata, accessible forms, secure APIs and a staging preview. Check permissions and a representative set of devices.
- **Launch with SEO protection.** Preserve useful URLs, map changed URLs with relevant permanent redirects, publish canonical and hreflang tags, submit a clean sitemap and monitor crawl errors.
- **Operate the new site.** Patch dependencies, review logs, protect admin access, back up content and rehearse rollback.
Google's site-move guidance recommends planning URL mappings and monitoring the move. A new design should not silently erase the pages that already answer customer searches. We measure both lead quality and technical health after launch.

## How IT Support in Tokyo can help

We can review your current WordPress and PHP setup, identify the highest-risk maintenance gaps, and recommend either a practical hardening plan or a phased React/Next.js migration. For a migration, our team handles content and URL inventory, bilingual Japanese and English page structure, server-rendered implementation, forms and integrations, launch checks, and ongoing improvement.

You receive an explanation of what should change, why it matters and what can remain. We can start with one representative page and a URL map so the scope, design and SEO risks are visible before a full rebuild.

![Editorial photograph of an IT team reviewing monitoring and maintenance after a website launch](/article-assets/wordpress-php-migration/postlaunch-operations.webp)

Editorial illustration: security work continues after a migration goes live.

## Know whether to patch or rebuild.

Tell us your current WordPress URL and the problems you need to solve. We will outline a sensible first review and the options for a secure, SEO-aware next step.

[Request a website and security review](/en/contact)

## Frequently asked questions

### Is WordPress itself unsafe?

No. A maintained WordPress site with supported plugins, patched PHP, controlled access and reliable hosting can be appropriate. Security depends on the whole system and its operating process.

### Will Next.js automatically improve SEO or security?

No. It provides tools for server rendering, metadata and routing. Useful content, correct redirects, dependency management and secure API design still require deliberate work.

### Can we keep WordPress as the content editor?

Possibly. A headless WordPress setup can keep familiar editing while a new frontend serves the public website. The WordPress backend still needs updates, access controls and hosting.

## Primary sources

Security details and platform guidance checked November 16, 2026. Verify current patches with your hosting provider.

- [PHP project: October 21, 2026 security announcement](https://www.php.net/archive/2026.php#2026-10-21-5)
- [Japan IPA: PHP2shell advisory and exploitation status](https://www.ipa.go.jp/security/security-alert/2026/alert20261022.html)
- [WordPress: critical PHP security release and impact](https://wordpress.org/news/2026/10/critical-php-security-release/)
- [WordPress: hardening guidance](https://developer.wordpress.org/advanced-administration/security/hardening/)
- [React: server-component security advisory](https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components)
- [Google Search Central: JavaScript SEO basics](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)
- [Google Search Central: site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)
Related: [WordPress to Next.js migration and SEO guide](/en/blog/migrate-wordpress-to-nextjs-seo-guide-japan) · [WordPress vs Next.js](/en/blog/wordpress-vs-nextjs-website-development-japan) · [Web development services](/en/services).

## Source

Canonical HTML: https://itsupportintokyo.com/en/blog/wordpress-php-security-2026-react-nextjs-migration
Other language: https://itsupportintokyo.com/ja/blog/wordpress-php-security-2026-react-nextjs-migration
Other language: https://itsupportintokyo.com/th/blog/wordpress-php-security-2026-react-nextjs-migration