Skip to content
Receipts, not vibes. See how your website actually scores against ours on our new website audit comparison tool!
PHP versions and the dates their security support ends, as published by the PHP project, with today's date markedWhich PHP versions still get fixes?Each bar ends on the day the PHP project stops fixing that version.2026202720282029PHP 8.1No security fixesPHP 8.2until Dec 31, 2026PHP 8.3until Dec 31, 2027PHP 8.4until Dec 31, 2028PHP 8.5until Dec 31, 2029Today, Oct 23

PHP 8.2 support ends on December 31. What does that mean for your website?

October 23, 2026

PHP runs underneath WordPress and many other sites. Version 8.2 stops getting security fixes at the end of the year. Here is how to check yours and whose job it is.

Nothing dramatic happens to your website on January 1. If it runs on PHP 8.2, it will keep loading, taking orders and sending form messages exactly as it does now. What changes is quieter: from that day, the PHP project stops publishing security fixes for 8.2, so any flaw discovered afterward stays open on your server for good.

The sensible response is to move to a newer PHP version before the end of the year, ideally 8.3 or later, and to do it with a test run first. For most small businesses this is a job for the hosting company or whoever runs the server, not for the owner. Your part is to find out which version you are on, ask the right person a clear question, and make sure someone checks the site afterward. The rest of this article explains each step, and why a PHP security release from October 21 makes the timing more pressing than usual.

What is PHP, and why does my website depend on it?

Quick answer: PHP is the programming language that runs on your web server and builds each page before it reaches a visitor. WordPress and many other website systems are written in it, so the PHP version sits underneath everything else.

Think of your website as a house. WordPress, your theme and your plugins are the rooms and furniture. PHP is the foundation and the wiring. You can repaint every room, and you should, but none of that touches the wiring behind the walls.

This is the point small businesses most often miss. Updating WordPress, installing plugin updates or switching themes does nothing for a flaw in PHP itself. The PHP version is chosen and installed on the server, which is usually managed by your host. A site can be perfectly current inside the WordPress dashboard and still run on a PHP version with known, unfixed problems underneath.

What PHP version am I on?

Quick answer: In WordPress, go to Tools → Site Health, open the Info tab and expand Server. The PHP version is listed there. Your hosting control panel shows it too.

Step by step:

  1. Log in to your WordPress admin as an administrator.
  2. Open Tools, then Site Health.
  3. Switch to the Info tab at the top of the page.
  4. Expand the Server panel and read the line for the PHP version.

Write the number down. If it starts with 8.3, 8.4 or 8.5, you have time to spare. If it starts with 8.2, the deadline in this article applies to you. If it starts with 8.1, 8.0 or a 7, you are already past the point where the PHP project issues updates, and this is worth raising with your host this week.

Not on WordPress, or no admin access? Most hosting control panels have a page called something like "PHP version", "PHP settings" or "Software". Failing that, ask your host or developer. It is a routine question, and they should answer it the same day.

What happens on January 1 if my site is still on PHP 8.2?

Quick answer: The site keeps working. But PHP 8.2 no longer receives security fixes from the PHP project, so any weakness found after December 31 will not be patched for that version.

The official PHP supported versions page sets the dates. Each PHP branch is supported for four years in total: active support first, then security fixes only. For the versions small business sites are likely to be running, the security support ends on:

  • PHP 8.2: December 31, 2026
  • PHP 8.3: December 31, 2027
  • PHP 8.4: December 31, 2028
  • PHP 8.5: December 31, 2029

PHP 8.2's active support actually ended back on December 31, 2024. Since then it has received security fixes only, and that last lifeline runs out at the end of this year. The release notes for PHP 8.2.35 put it plainly: 8.2 reaches end of life on December 31, 2026 and gets no further security fixes after that.

An unsupported version is not instantly dangerous. It becomes riskier over time, as new problems are found and published and your server has no official fix for them. The longer a site stays on it, the larger that pile becomes. Some Linux distributions and paid long-term support vendors do continue to patch older PHP versions for their own customers, so a host may be covered in ways that are not visible to you. That is exactly why the right move is to ask, rather than assume either way.

Why does the October 21 security release make this urgent?

Quick answer: On October 21, the PHP project fixed two critical flaws that can let an attacker run code on a server without logging in. Updating PHP is the only complete fix, and that update is your host's to apply.

According to the PHP news archive for 2026, PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fixed two vulnerabilities, CVE-2026-109618 and CVE-2026-109619. The advance notice rated both at 9.2 on CVSS version 4.0, which is in the critical range. The project says they can allow unauthenticated remote code execution, meaning an outsider could make the server run their instructions without an account.

A few details from the advisory are worth knowing, even if you never touch a server yourself:

  • There is no complete workaround. The PHP team describes some configuration changes that reduce exposure to specific attack paths, but says only an update is a complete solution.
  • Every web-facing PHP setup is in scope, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.
  • mod_php carries the highest risk, according to the advisory, which describes a demonstrated exploit where a single unauthenticated request triggers the attack before any website code runs.
  • Older versions got only partial help. Because of the severity, the security team published minimal source-code backports for PHP 7.4, 8.0 and 8.1, aimed at people who build PHP themselves or have no long-term support vendor. That is not the same as a normal release your host can install with one command.

So there are two separate tasks here. In the short term, your host needs to have applied the October 21 releases, whatever version you run. In the longer term, anyone on 8.2 needs a plan to move up before the year ends, because the next critical PHP flaw after that date will not get an 8.2 release at all.

Whose job is this, mine or my host's?

Quick answer: On almost every small business plan, installing and updating PHP belongs to the hosting company or the person who manages your server. Choosing when to switch versions is often shared, because you or your developer may need to confirm the site still works.

It helps to know which kind of hosting you have:

  • Managed WordPress hosting. The host runs the server, applies PHP security releases and usually schedules version upgrades. You may be offered a button to switch versions yourself.
  • Shared hosting with a control panel. The host patches PHP, but the version your site uses is often a setting you choose. Some hosts move customers off old versions automatically with notice; others leave the choice to you indefinitely.
  • A server or virtual machine you rent and manage. Then PHP is genuinely your responsibility, or your developer's. If nobody is sure who that is, that uncertainty is the most important thing to fix.

If you do not know which category you are in, here is a message you can send to your host or developer as written:

"Which PHP version does our website run on? Have the October 21, 2026 PHP security releases been applied to our server? What is the plan for moving us off PHP 8.2 before its security support ends on December 31, and will we get a chance to test the site first?"

Do I need to do anything on managed hosting?

Quick answer: Less than on other plans, but not nothing. Confirm the October releases were applied, find out when your site will move off 8.2, and arrange for someone to check the site after the switch.

Managed hosts are generally good at patching. Where things go wrong is the version change, because the host can update PHP but cannot know whether your eight-year-old booking plugin still works on the newer version. Many managed hosts give customers a window to upgrade on their own schedule and then move any remaining sites in bulk. If yours does that, you want to be the one choosing the date, after a test, not finding out from a broken contact form.

The WordPress requirements page currently recommends PHP 8.3 or greater. It also notes that WordPress still works on PHP 7.4 and later in older environments, while warning that versions past end of life may expose a site to security vulnerabilities. Asking your host for 8.3 or newer puts you in line with WordPress's own recommendation.

Will upgrading PHP break my site?

Quick answer: WordPress itself handles newer PHP versions well. The usual trouble comes from old plugins and themes that have not been updated in years. Testing on a copy of the site first, with a way back, removes most of the risk.

Each new PHP version removes or changes a few older behaviors. Well-maintained code keeps up; abandoned code does not. When something breaks after a PHP upgrade, it tends to look like one of these:

  • a blank white page, or a "critical error" message on part of the site;
  • a contact, booking or donation form that appears to send but never arrives;
  • a checkout that fails at the final step;
  • an admin screen that will not load, often belonging to one particular plugin.

You can reduce the risk before anyone touches the live site:

  1. List your plugins and theme, and note when each was last updated by its author. Anything untouched for several years is the most likely culprit.
  2. Update everything that has an update waiting, on the current PHP version, so you are testing the newest code.
  3. Make a staging copy. Many hosts offer a one-click staging site. Switch only the staging copy to the newer PHP version.
  4. Test what earns you money or trust. Submit every form, place a test order, try the booking calendar, log in as an editor.
  5. Keep a rollback ready. Take a full backup, and confirm with your host that you can switch the PHP version back quickly if something slips through.
  6. Then switch the live site, at a quiet time, and repeat the checks straight away.

If a plugin fails on the newer version and its author has stopped maintaining it, that is useful to learn now, while you have weeks to find a replacement rather than hours.

Which businesses should be most concerned?

Quick answer: Start with sites that take payments or hold personal information: donation pages, online shops, booking forms that ask about health, and anything in healthcare, finance or real estate. These have the most to lose from an unpatched server.

A flaw that lets someone run code on your server is a flaw that can expose whatever passes through it. The businesses that should move first:

  • Nonprofits taking donations online. Donor names, addresses and payment pages make an appealing target. See our nonprofit industry page.
  • Any shop with a checkout, including a bakery taking cake orders and deposits online. Our bakery page talks about how small food businesses use their websites.
  • Spas, studios and wellness practices whose booking forms ask about health conditions or injuries. See wellness.
  • Healthcare practices, financial firms and real estate offices, where forms gather patient details, financial circumstances or a buyer's plans. Our pages for healthcare, financial services and real estate cover each in more depth.
Loam's example website for Loam Grown Community Food Bank, a fictional nonprofit, on a laptop beside a phoneLoam's example website for Loaf & Loam Bakery, a fictional bakery, displayed on a laptop and a phone togetherLoam's example website for Loam & Behold Wellness, a fictional day spa, shown across a laptop screen and a phone, in dark mode

Those are Loam's example sites, built for made-up businesses so we never have to put a client's work on display. The food bank, the bakery and the spa are fictional; their websites, editors and forms are real. All ten are in our custom website examples, and each has its own page on our industries page.

Is this a reason to leave WordPress?

Quick answer: On its own, no. Every PHP-based system faces the same version calendar. It is worth considering a move if your site depends on old plugins that will not survive the upgrade, or if nobody clearly owns the server.

PHP upgrades are a normal part of running a WordPress site, and a host that handles them well makes them nearly invisible. They become a reason to rethink when the upgrade exposes deeper problems: a site held together by abandoned plugins, a developer who has moved on, or a growing sense that every maintenance task is a gamble.

If your staging test turns up a long list of failures, you face a choice between repairing the existing site and rebuilding it. Rebuilding is often the better value when the site is due a redesign anyway. If you want to see what moving off WordPress involves, our WordPress migration page explains how pages, web addresses and search standing are carried across, and our websites service describes what we build instead. Staying is a perfectly good answer too, as long as someone owns the upkeep.

What does a Loam website do differently?

Quick answer: A Loam site is built on a different stack (Next.js and Payload CMS, hosted on Vercel), has no plugin marketplace, and gets a monthly review of security and dependencies by a person, with a report sent to you.

We will not claim any website is beyond attack. The differences are about how much there is to look after and who looks after it, as our example sites describe:

  • Built-in features instead of plugins. Everything is maintained together, so there is no collection of add-ons from different authors to keep compatible.
  • Someone checks every month. A person reviews security and the software the site depends on, and you receive a plain-language report of what was done.
  • You own the parts that matter. Your domain is in your name and your content lives in a database account you own, so nothing is held hostage if you move on.
  • Less exposed by design. No public data API, no secrets in the page, no default admin passwords, and forms that filter out spam.

If you are not sure where your site stands on PHP, or what a sensible plan before December 31 looks like, send us a note and we will help you work it out, whether or not that ends with a new website.

Questions readers ask next

Some do, with notice, and some leave it to you indefinitely. Check your host's announcements or ask them directly, so you can choose the date and test first rather than discover the change after it happens.

Often a little, because each release improves performance. Treat speed as a pleasant side effect, not the reason to upgrade. The reason is continued security fixes.

A staging site is a private copy of your website where changes can be tested without visitors seeing them. Many hosting plans include one, sometimes as a single button; your host's help pages will say.

Usually not, beyond keeping WordPress, plugins and themes updated. Check the Site Health screen afterward for new warnings, and test your forms and checkout once more a day later.

It can buy time for a site that genuinely cannot upgrade yet, such as one waiting on a rebuild. It is a bridge, not a destination, so pair it with a plan and a date for moving up.