PHP2Shell on Staatic Cloud: protection and patching
Every Staatic Cloud site now runs PHP with the fix. Published sites run no PHP, and origins require a login, apart from origin rules and some endpoints.
Visitors and bots get finished pages, fast, from 250+ locations. Your WordPress stays private: no login page, plugin code or database to break into.
/wp-login.php
200
Login page found
404
Not found
/xmlrpc.php
405
XML-RPC answers
404
Not found
/wp-json/wp/v2/users
200
1 user name listed
404
Not found
/wp-admin/admin-ajax.php
400
Plugin code reachable
404
Not found
WordPress runs 39.5% of all websites, so one working exploit can be pointed at millions of sites. Taking the targets off the public site doesn't depend on how fast you patch. W3Techs
Your team works in your WordPress:
Only your team gets in.
The login page, plugin code and database stay inside it. Pages leave it once, when you publish, and nothing comes back in.
Finished pages at 250+ locations.
They are sent from there to whoever asks.
Every visit, your site gets:
Without Staatic every visit runs, bots included: Web server WordPress Database
We request the addresses bots try first, plus your homepage, and show what comes back.
We only request public addresses, the same ones bots try all day. Only check sites you own or manage.
Your site
Staatic
Found through files your homepage loads. Plugins that load nothing there can still be active.
(license)
staatic.com is served the way yours would be on Staatic Cloud. From our WordPress, with no page cache, the same homepage took 249 ms to its first byte.
GET https://staatic.com/
51 requests, 29 October 2026
From a location in Amsterdam, not a global average. Every Staatic request was a CloudFront cache hit.
See the measurementsTest staatic.com on Google PageSpeed Insights
Publish your site the same way. Free for 14 days, no payment details needed.
Start your free trialPublish your site the same way. Free for 14 days, no payment details needed.
Start your free trialA new plugin flaw can't be used against your public site, so updates go back to being routine instead of an emergency.
Every page is already finished and served from 250+ locations: 47 ms to first byte in our test.
If WordPress breaks, visitors keep getting the last version you published. A traffic spike means sending the same pages more often.
Forms, search and redirects keep working on the static site, and your team works in WordPress as before.
Forms and search need Staatic Premium or Staatic Cloud.
See all featuresWhat you still look after
Keep WordPress updated, turn on two-step verification for your accounts and publish from a clean site. The full list.
Run every client site from one Staatic Cloud account. A new plugin flaw can't be used against the public sites, so it stops being a same-night emergency.
Keep writing in WordPress. Staatic Cloud hosts it and the public site, backups included, so there is no server to run. You keep WordPress and its plugins updated.
A WordPress plugin that publishes to Staatic Cloud, SFTP, Amazon S3, GitHub or Netlify, from the dashboard or WP-CLI. On Staatic Cloud, origin rules forward the paths that must stay dynamic.
“Staatic is an excellent solution for us. It brings all our clients’ hosting under one dashboard and enables the sites to be fast and secure. The support we have got is second to none and we highly recommend this service.”
“Staatic helped us turn our dynamic mess into a lightning-fast static website. The hosted backend environment, combined with the flexibility of the WordPress plugin, gives us great control over everything from publishing to redirects. Their support is incredibly fast and helpful. Highly recommended!”
“We were spending hours every month patching plugins and chasing performance. Staatic eliminated that work entirely. Publishing is straightforward, the site stays consistently fast, and our team can focus on content again instead of WordPress maintenance.”
Every Staatic Cloud site now runs PHP with the fix. Published sites run no PHP, and origins require a login, apart from origin rules and some endpoints.
PHP2Shell is a pair of critical PHP interpreter bugs, fixed in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Where to patch and what a static public site changes.
CVE-2026-87902 lets an anonymous request make WordPress core include a local PHP file. Whether that leads to code execution takes minutes to check.
Try it on your own site for 14 days.