PopularLegacy PHP & WordPress modernization

New PHP vulnerabilities? Here’s a calm next step.

PHP released fixes for two critical vulnerabilities on October 21, 2026. If your website runs on legacy PHP or an older WordPress setup, start with a free risk check. We’ll tell you where you stand in plain English, what to fix first, and how to get onto supported, patched versions.

  • Since 1996
  • WordPress, Drupal, Joomla & HubSpot experience
  • WordPress to AI-native migrations

Free · No obligation

Free legacy PHP & WordPress risk check

A few quick questions. We’ll look at your site and reply with where you stand and what to do first. No obligation.

It runs on (optional)
PHP version, if you know it (optional)

We’ll only use your details to reply about your risk check. Privacy policy. Prefer to talk? Call (781) 704-3121.

01October 21, 2026

What happened, in plain English

Serious, and fixable. For most sites the first step is a PHP update. That’s where we start.

On October 21, 2026, the PHP project released security updates for two critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619. PHP’s advisory says they can allow unauthenticated remote code execution: someone could run their own code on an unpatched web server without logging in.

PHP says every PHP installation serving web requests is at risk, and that only an update is a complete fix. PHP 8.1 and older no longer receive updates from the PHP project at all.

WordPress.org says the vulnerabilities are not specific to WordPress, and no WordPress update is required. What matters is the PHP version your server runs. In WordPress you can see it under Tools > Site Health > Info > Server, or ask your host.

2 critical vulnerabilities fixed
CVE-2026-109618 and CVE-2026-109619
9.2 CVSS v4.0 score, each
Rated critical in PHP’s advisories
8.2.35 or newer on PHP 8.2
Fixed in 8.5.12, 8.4.27, 8.3.36 and 8.2.35
8.1 and older get no fix
No longer updated by the PHP project

Sources, as of October 21, 2026: PHP security advisory, php.net, GHSA-w8hw-w9fx-j79w (CVE-2026-109618), GHSA-6wmf-4rv5-p3rp (CVE-2026-109619), NVD: CVE-2026-109618, NVD: CVE-2026-109619, WordPress.org: Critical PHP Security Release, PHP supported versions.

02Sound familiar?

Signs your site needs more than a patch.

  • 01Your PHP version is older than you’d like to admit.

    Your server runs PHP 8.1 or older, which no longer gets updates from the PHP project. Or nobody knows which version you’re on.

  • 02WordPress updates keep getting put off.

    Core, plugins or the theme haven’t been updated in months, because something broke last time.

  • 03A plugin you rely on has gone quiet.

    Its developer stopped shipping updates, and your site still depends on it.

  • 04Nobody wants to touch it.

    The site was built by someone who has moved on, and the code is a mystery.

03How it works

From risk check to modern, in five steps.

  1. 01Risk check

    Free. We look at your site, your platform and what we can see of your PHP and WordPress versions, and tell you where you stand and what to fix first.

  2. 02Stabilize

    Backups first. Then we update you to a supported PHP version and bring WordPress core, plugins and theme up to date, testing as we go so nothing breaks in front of customers.

  3. 03Plan

    You choose the path: a modern, well-maintained WordPress site, or an AI-native site built on React. We quote it up front.

  4. 04Migrate

    We move your content, keep your URLs or redirect them, rebuild forms and integrations, and protect the search rankings you’ve earned.

  5. 05Look after it

    Launch, then keep it current: updates, monitoring and quick edits, so you never end up here again.

04Where you end up

Two ways forward. You choose.

Stay on WordPress

Modern WordPress

Keep the CMS your team already knows, rebuilt on supported PHP with a clean theme and only the plugins you need.

  • Supported, patched PHP and WordPress
  • Fewer, well-maintained plugins
  • Your team keeps editing the way it does today

Leave legacy PHP behind

AI-native

A fast, modern site built on frameworks like React, with assistants like Claude built in. We migrate you from WordPress for you.

  • Built on frameworks like React
  • AI assistants built in
  • A WordPress to AI-native migration, handled end to end

05Why Backbone

Calm hands since 1996.

1996
Founded in Boston as one of the first SEO firms. When we migrate a site, protecting your search rankings is part of the job.
WordPress to AI-native
We build everything from WordPress sites to AI-native sites built on frameworks like React, and we move clients from one to the other.
CMS migrations
Our development team has worked with WordPress, Drupal, Joomla and HubSpot, and has migrated sites from one CMS to another.
One team
Strategists, designers, writers, developers and project managers, working as an extension of your team.

See our website and CMS migration work · Contact us

06Questions

Straight answers.

Is my site affected?

It depends on which PHP version your server runs, how it is configured, and what runs on top of it. That is exactly what the free risk check is for. If you’d rather not wait, ask your host which PHP version your site uses and whether it is still supported.

We run WordPress. Is WordPress the problem?

WordPress runs on PHP, so it depends on your server’s PHP version as well as WordPress core, your plugins and your theme. Keeping all four current is what matters.

Do we have to rebuild the whole site?

Usually not right away. The first step is often getting onto a supported, patched PHP version and updating what’s on top of it. A rebuild or migration comes next, when it makes sense for you.

Will we lose our search rankings?

Not if the migration is done carefully. We started out in 1996 as one of the first SEO firms, so we plan URLs, redirects and content before anything moves.

What does an AI-native site mean?

A modern site built on frameworks like React instead of a legacy PHP stack, with AI assistants like Claude built in where they help your visitors and your team.

What does it cost?

The risk check is free. Upgrades and migrations are quoted up front, so you know the price before we start. Ongoing care can be part of a monthly retainer.

We’re on PHP 8.2. Are we fine?

Update to 8.2.35 or newer now. Then plan your next move: php.net lists December 31, 2026 as the end of security support for PHP 8.2.

Can you just patch it while we decide?

Yes. Stabilizing first and deciding on the bigger move later is a perfectly good plan.

Not quite the right fit?

That’s okay. We understand our limits. If what you need is bigger than, or different from, what we offer, tell us anyway. We’re happy to guide you toward offerings we know well that can get you the outcome you’re after.

Get your free risk check.

Tell us your site and what worries you. We’ll reply with where you stand and a calm plan for what to do first.

PHP is a project of The PHP Group. WordPress is a trademark of the WordPress Foundation. Backbone Media is an independent agency and is not affiliated with or endorsed by The PHP Group, The PHP Foundation, the WordPress Foundation or Automattic.

Free PHP & WordPress risk check