I will patch and update PHP on your vps or cpanel server


About this gig
PHP just patched two critical flaws (CVE-2026-109618 and CVE-2026-109619, "php2shell") that allow remote code execution with no login. Attacks are already being reported. If your server runs PHP below 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or still uses 7.4, 8.0 or 8.1, it needs attention now.
Your host can't patch a VPS or dedicated server for you. I can, safely and without breaking your sites.
What I do:
Confirm a snapshot/backup before touching anything
Update PHP via cPanel/EasyApache, Plesk, CloudLinux or apt/dnf
Restart PHP-FPM/Apache so the fix actually loads
Verify every PHP version on the server, CLI and web
Apply interim mitigations if an update isn't available yet
Check for signs of compromise: cron jobs, unknown files, processes
Move old PHP 7.4/8.0/8.1 sites to a supported 8.x (Premium)
Works with Ubuntu, Debian, AlmaLinux, Rocky, RHEL, cPanel/WHM, Plesk, CloudLinux and any VPS provider.
Access: a temporary SSH key or panel user that you remove afterwards. Never your root password.
You get a short report: versions before/after, what changed, what to watch.
Send me your php -v output and control panel name, and I'll confirm the right package.
Respect third-party rights
Please be aware that it is against Fiverr's policies for sellers to include themes, templates, or any other elements that infringe third-party rights or applicable laws in the delivered work. Read more about in our Guide to Responsible Digital Creation.
Get to know Alesson
Shopify Developer Theme, Performance, Apps
- FromCanada
- Member sinceSep 2026
- Avg. response time1 hour
Languages
Portuguese, English, French
FAQ
My host emailed me about a PHP vulnerability. Is this the right gig?
Yes. Hosts can’t patch unmanaged VPS or dedicated servers. I apply the update, restart PHP and verify the patched version is actually running.
Will updating PHP break my website?
A patch update within the same version (e.g. 8.3.x to 8.3.36) is very low risk. Moving from 7.4/8.0/8.1 can break old code, so Premium tests on a copy first and fixes errors.
Do you need my root password?
No. Create a temporary user with an SSH key I send you, or a temporary WHM/Plesk login. Remove it after delivery.
Why is a restart needed?
PHP-FPM and Apache keep old code in memory. Without a restart the vulnerable version keeps running even after the update installs.
"php -v" shows an old number after the update. Is it patched?
Possibly. Debian, Ubuntu and RHEL often backport fixes without changing the version. I check the package changelog for the CVE, not just the number.
I’m on PHP 7.4 / 8.0 / 8.1. What now?
The PHP project no longer releases these. Best fix: upgrade to 8.3 or 8.4 (Premium). If you can’t yet, I apply vendor builds or interim mitigations to reduce exposure.
Can you guarantee my server won’t be hacked?
No honest seller can. I guarantee the PHP patch is installed, loaded and verified, and I report anything suspicious I find.
Do you work with shared hosting?
Shared hosting is patched by your host. I can still switch your account to a supported PHP version in cPanel and test your site.

