Rebuild an old PHP website on a supported stack
PHP 8.1 and older will never get an official fix for PHP2Shell. If your site can't simply move to a newer PHP version, we rebuild it on a current, supported stack and keep its design, content and page addresses.
Who this is for
Sites on PHP 5.x, 7.x, 8.0 or 8.1, which get no official PHP2Shell fix.
Sites that break when the host switches to a newer PHP version, usually because of old themes, plugins or custom code.
Owners whose original developer is gone and who can't safely update the site themselves.
PHP 8.1, 8.0 and 7.4 are end of life
End of life means the PHP project no longer publishes security fixes for that branch. PHP2Shell will never get an official fix in these versions.
| Branch | Security fixes ended | PHP2Shell fix |
|---|---|---|
| PHP 8.1 | None from the PHP project | |
| PHP 8.0 | None from the PHP project | |
| PHP 7.4 | None from the PHP project |
Some Linux distributions and extended-support vendors still patch old branches. If your server relies on one of them, ask for written confirmation that PHP2Shell is covered. Otherwise the site needs to move to a newer PHP version or be rebuilt.
Your three options
A rebuild isn't always needed. These are the ways out, from least to most work.
Upgrade PHP in place
If the code runs on PHP 8.3 or newer with small fixes, this is usually the cheapest path. Test it on a copy of the site first. The upgrade guide has the steps for each control panel.
Buy extended support
Vendors such as Zend and TuxCare sell security patches for old PHP branches. It buys time, but the code stays old.
Rebuild on a supported stack
When the code can't move forward, the site is rebuilt to run on software that still gets security fixes.
How it works
Send the address
Use the form on this page with your site's address and what you'd like. That's all we need to start.
Get a quote by email
We look at the site and reply by email with a quote for the work.
Decide
Nothing starts until you accept the quote.
Rebuild and switch over
We build the new version with the same page addresses and switch the site over once it works.
What you get
Same site, new foundation
Your design, content and page addresses stay as they are, so visitors and search engines see the same site. Only what runs underneath changes.
Or improve it while we're at it
Tell us what you'd like to change, from a new layout to faster pages, and we'll include it in the quote.
A clear quote before any work
Send us the address and what you want. We reply by email with a quote, and nothing starts until you agree to it.
Questions about a rebuild
What does PHP 8.1 end of life mean for my site?
Since 31 December 2025 the PHP project publishes no security fixes for 8.1, including the PHP2Shell fix. The site keeps running, but every new flaw stays open. Move to PHP 8.3.36 or newer, or rebuild the site if its code can't move.
Will my search rankings survive the rebuild?
Your page addresses stay the same, so links and search results keep pointing to the right pages. That's the main thing that protects rankings during a rebuild.
Can't I just change the PHP version in my hosting panel?
Try it on a copy of the site first. Old themes, plugins and custom code often stop working on PHP 8.2 or newer. If the site still works, you don't need a rebuild.
Does a rebuild fix PHP2Shell?
Yes. The rebuilt site runs on software that still gets security fixes, so PHP2Shell and future flaws are fixed by normal updates. You can confirm it afterwards with the checker.