PHP 5.6 and 7.0 End Security Support: How Websites Should Upgrade PHP

At the end of 2018, two popular PHP branches, 5.6 and 7.0, reached end of life. According to PHP's supported versions page, 5.6 stopped on 31/12/2018 (final release 5.6.40), while 7.0 had its final release 7.0.33 and is recorded as ending support on 10/1/2019. Since then, these branches no longer receive security patches. If your WordPress website still runs old PHP, it's time to plan an upgrade.

Why upgrade PHP

• Security: newly discovered vulnerabilities won't be patched on versions that are no longer supported.
• Performance: PHP 7.x and later versions generally run faster than 5.6 and use less memory.
• Compatibility: new plugins and themes increasingly require higher PHP versions.

Upgrading PHP doesn't change your post content, but it can expose errors in old themes or plugins, so test before applying to the live website.

Suggested PHP upgrade process

Step 1: Check the current version. Look in the hosting control panel or ask your provider. Some diagnostic plugins also show the PHP version.

Step 2: Back up everything. Back up both files and the database, and check that the backup can be restored.

Step 3: Update WordPress, themes and plugins. Move to the latest versions and remove plugins you no longer use. Check each plugin's description page to see whether it lists PHP compatibility.

Step 4: Test on a copy (staging). If your hosting supports it, create a copy of the website, change PHP on that copy, and browse the main pages, forms, checkout and admin login.

Step 5: Change the PHP version on the live website. Choose a branch that is still supported. At this time, branches 7.1, 7.2 and 7.3 are still in their support period; see the current version table at php.net and WordPress's recommendations. Do it when there are few visitors.

Step 6: Check after the change. Open the home page, posts, product pages, cart and contact form. Look at the error log for warnings.

Step 7: Be ready to roll back. If you hit a serious error, switch back to the old version right away to keep the website running, then find the cause on the copy.

Common errors after upgrading

• White screen or 500 error: usually caused by an old plugin or theme using a function that's no longer supported. Disable the suspect plugin by renaming its folder via FTP or a file manager.
• "Deprecated" warnings: not a blocking error yet, but a sign the code needs updating.
• Lost connection to external services: due to a missing PHP extension; ask your hosting provider to enable it.

If a theme or plugin is developed by a third party and no longer updated, consider replacing it with a maintained solution.

When to ask for help

Websites that sell products, take bookings or have many customizations should have a technical person on hand during the switch. If you need help, you can contact HVSC's Technology team.

2026 update: Later WordPress versions have a Tools > Site Health section to view the PHP version. PHP 5.6 and 7.0 have long been obsolete; the 7.x branches themselves are also out of support. According to the WordPress.org requirements page, the current recommendation is PHP 8.3 or higher, while the minimum is listed as 7.4 (and those versions are also end-of-life). Check php.net and WordPress.org again when planning.

FAQ

I don't know which PHP my website uses. Where do I ask?

Look in the hosting control panel, or ask your hosting provider.

Will upgrading PHP lose data?

Changing the PHP version doesn't delete data, but back up first in case of compatibility errors.

Can I jump straight to the latest version?

You may be able to if your theme and plugins are compatible, but test on a copy first and upgrade step by step if you hit errors.

Reference sources

• PHP.net — Unsupported Branches: https://www.php.net/eol.php
• PHP.net — Supported Versions: https://www.php.net/supported-versions.php
• WordPress.org — Requirements: https://wordpress.org/about/requirements/
• WordPress.org — Update PHP: https://wordpress.org/support/update-php/