{"id":89820,"date":"2026-11-02T23:41:47","date_gmt":"2026-11-02T23:41:47","guid":{"rendered":"https:\/\/www.wpstaq.com\/?p=89820"},"modified":"2026-11-03T03:36:08","modified_gmt":"2026-11-03T03:36:08","slug":"post-php2shell-black-october","status":"publish","type":"post","link":"https:\/\/www.wpstaq.com\/sg\/post-php2shell-black-october\/","title":{"rendered":"Here&#8217;s what the recent PHP2Shell has taught us"},"content":{"rendered":"<p>What is now called Black October, the recent php2shell vulnerability caught everyone&#8217;s pants down. The PHP2Shell incident had developers, hosting companies and digital agencies checking their infrastructure while answering the question every client understandably wanted answered: <strong>\u201cAre we protected?\u201d<\/strong><\/p>\n<p>Then came the familiar commentary. WordPress isn\u2019t secure. Move to Shopify. Use Webflow. Build a static website. Get AI to build something custom.<\/p>\n<p>If only security were that simple.<\/p>\n<p>I\u2019m not going to give you another breakdown of the incident. Instead, I want to talk about what comes next, what agencies should understand, and why the company looking after your infrastructure matters more than a reassuring list of security features. Because another vulnerability will come along. The useful question is how prepared you are to deal with it.<\/p>\n<h2>Is WordPress secure?<\/h2>\n<p>The short answer is that WordPress can be run securely. But a meaningful answer needs to look beyond WordPress itself.<\/p>\n<p>Your website sits on a whole stack of software. There\u2019s the operating system, the web server, the database, PHP and the libraries that handle things such as images and compressed files. Then there\u2019s WordPress core, your plugins and your theme.<\/p>\n<p>Each of those layers needs looking after.<\/p>\n<p>You could have WordPress fully updated, every plugin current and no known vulnerabilities in your theme, while a vulnerable component sits underneath the whole thing.<\/p>\n<p>Your WordPress dashboard can show a lovely row of green ticks without telling you much about the server running it.<\/p>\n<p>That\u2019s why the hosting partner matters. Someone needs to take responsibility for the parts of the environment you don\u2019t see when you log in to WordPress.<\/p>\n<h2>Changing platforms doesn\u2019t make security disappear<\/h2>\n<p>There are perfectly good reasons to choose Shopify, Webflow, Wix or a static website. Different tools suit different jobs, and some architectures give attackers fewer opportunities.<\/p>\n<p>But \u201cwe moved away from WordPress, so security is sorted\u201d is a very comfortable assumption to make.<\/p>\n<p>Every platform relies on code. Hosted services have infrastructure and dependencies. Custom websites have application logic, permissions and integrations. Static websites still have build processes, deployment accounts and, often, external services.<\/p>\n<p>The responsibilities change. They don\u2019t disappear.<\/p>\n<h3>Examples across the ecosystem<\/h3>\n<p>The following examples are from 2026, through 3 November. They affect different components and have different consequences, so this is not a ranking or a claim that every platform carries the same risk.<\/p>\n<p>&nbsp;<\/p>\n<table>\n<tbody>\n<tr>\n<th>Platform or approach<\/th>\n<th>Summary<\/th>\n<th>What was affected<\/th>\n<\/tr>\n<tr>\n<td><strong>WordPress<\/strong><\/td>\n<td>Upgrade-process remote code execution, fixed in WordPress 7.1.4 on 28 October.<\/td>\n<td>WordPress core itself. A weakness could allow code execution during the upgrade window.<\/td>\n<\/tr>\n<tr>\n<td><strong>Webflow<\/strong><\/td>\n<td>Brotli compression-library vulnerability, CVE-2026-111497.<\/td>\n<td>An infrastructure dependency. Webflow reported remediation work and no evidence of exploitation or impact to customer data or availability.<\/td>\n<\/tr>\n<tr>\n<td><strong>Shopify ecosystem<\/strong><\/td>\n<td>Cross-shop authorisation bypass, CVE-2026-63414, fixed in <code>shopify_app<\/code> 23.0.3.<\/td>\n<td>Certain apps using Shopify\u2019s library could confuse which shop a requester was authorised to access. This did not affect every Shopify storefront.<\/td>\n<\/tr>\n<tr>\n<td><strong>Wix<\/strong><\/td>\n<td>SVG-upload cross-site scripting, CVE-2026-2276.<\/td>\n<td>The reported issue concerned Wix\u2019s account-settings application, where an uploaded SVG could contain executable JavaScript. The supplied material does not establish a vendor remediation date.<\/td>\n<\/tr>\n<tr>\n<td><strong>Astro<\/strong><\/td>\n<td>Code execution through AVIF image optimisation, fixed in Astro 7.2.8.<\/td>\n<td>An image-processing dependency chain, where an attacker could cause an affected installation to process an untrusted image.<\/td>\n<\/tr>\n<tr>\n<td><strong>EmDash CMS<\/strong><\/td>\n<td>HTML-sanitiser dependency vulnerability, CVE-2026-44990.<\/td>\n<td>A dependency that could allow content intended to remain harmless text to become executable HTML or JavaScript. Exploitability depended on how that output was used.<\/td>\n<\/tr>\n<tr>\n<td><strong>Lovable<\/strong><\/td>\n<td>Exposure of public-project chat history and source code, affecting 3 February\u201320 April.<\/td>\n<td>Access controls around public projects. According to Lovable\u2019s report, private projects and Lovable Cloud were unaffected.<\/td>\n<\/tr>\n<tr>\n<td><strong>Static websites<\/strong><\/td>\n<td>LiquidJS HTML-filter bypass, CVE-2026-44644.<\/td>\n<td>A build or template process could let malicious HTML into the generated output if it relied on the affected filter to sanitise untrusted content. This was not a flaw in all static websites.<\/td>\n<\/tr>\n<tr>\n<td><strong>Vercel<\/strong><\/td>\n<td>Confirmed breach of internal systems in April 2026<\/td>\n<td>Attackers compromised Context.ai, a third-party AI tool used by a Vercel employee, then used the employee\u2019s account to access internal Vercel systems. Environment variables belonging to a limited subset of customers were compromised, prompting credential-rotation notices.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The point is straightforward: choosing a different platform changes your security considerations. It doesn\u2019t excuse you from having any.<\/p>\n<h2>Why are we hearing about so many vulnerabilities?<\/h2>\n<p>A newly discovered vulnerability isn\u2019t necessarily a newly introduced vulnerability.<\/p>\n<p>Some weaknesses can sit in software for years before someone finds the right conditions to expose them. A function might appear safe in isolation, then behave very differently when it receives an unexpected input or interacts with another component.<\/p>\n<p>Finding those combinations takes time, expertise and persistence.<\/p>\n<p>AI can help accelerate that work. It can assist researchers in reviewing code, exploring combinations and testing ideas at a scale that would be difficult to achieve manually by humans.<\/p>\n<p>That doesn\u2019t mean every vulnerability being reported was found by AI. And it certainly doesn\u2019t mean every piece of software is about to be hacked tomorrow.<\/p>\n<p>But I do think we should prepare for a world where weaknesses are found and investigated faster.<\/p>\n<p>There\u2019s a positive side to that: finding a vulnerability gives us an opportunity to fix it. Leaving it undiscovered doesn\u2019t make the software safer.<\/p>\n<p>The challenge is what happens between discovery and protection.<\/p>\n<p>A patch being available is useful. A patch being deployed across the environments that need it is what actually gets the job done.<\/p>\n<h2>How Staq responded to PHP2Shell<\/h2>\n<p>Back in March 2026, we launched a major infrastructure upgrade. The work behind it had started almost two years earlier.<\/p>\n<p>When I look back at that decision, incidents like PHP2Shell make its value very clear.<\/p>\n<p>Infrastructure work isn\u2019t always exciting to show off. You can\u2019t explain all of it with a screenshot or a new button in the dashboard. But when something urgent happens, you quickly find out whether that investment was worthwhile.<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>For us, it was.<\/strong><\/span><\/p>\n<p>After identifying a temporary mitigation shared on X, we disabled <code>session.upload_progress.enabled<\/code> across our infrastructure. That mitigation was in place <strong>10 hours before the official PHP patch was released<\/strong>.<\/p>\n<p>When the PHP update became available, we updated our entire infrastructure <strong>within three minutes<\/strong>.<\/p>\n<p>Our Staq users didn\u2019t have to do anything.<\/p>\n<p>They didn\u2019t need to log in, change PHP settings or work out which server needed attention. We handled the infrastructure response.<\/p>\n<p>That\u2019s the experience I want agencies to have. You already have clients looking to you for answers. You should have someone, like Staq on your side too.<\/p>\n<h3>The work started long before the incident<\/h3>\n<p>Those three minutes were made possible by the infrastructure and deployment processes we had already built and launched back in March 2026.<\/p>\n<p>We had invested in making updates across our infrastructure to be seamless, fast and efficient. Most importantly, not affecting any of our users.<\/p>\n<p>It appears that based on how fast and efficient we were able to roll this out, it appears that peers in our industry could not run as efficient as our infrastructure.<\/p>\n<h2>How did other hosts respond?<\/h2>\n<p>The <a href=\"https:\/\/www.activeset.co\/blog\/php2shell-host-status\">ActiveSet PHP2Shell host-status report<\/a> collected public updates from several providers. The timings cited in that report and the accompanying material illustrate how differently a rollout can progress.<\/p>\n<p>They also need context. A temporary mitigation, firewall protection and a completed software update are different milestones. A provider\u2019s public announcement time may not be the exact moment protection took effect.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Provider<\/th>\n<th>Response described in the supplied material<\/th>\n<\/tr>\n<tr>\n<td><strong>WordPress.com, WordPress VIP and Pressable<\/strong><\/td>\n<td>Automattic announced readiness <strong>seven hours before release<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td><strong>Pantheon<\/strong><\/td>\n<td>Supported live sites were reportedly patched in about <strong>six hours<\/strong>, with LTS completed later. Free and sandbox environments followed separately, while network filtering remained in place.<\/td>\n<\/tr>\n<tr>\n<td><strong>WP Engine<\/strong><\/td>\n<td>Reported completed deployment at 01:19 UTC on 22 October, <strong>approximately 12 hours into the cited timeline<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td><strong>Acquia<\/strong><\/td>\n<td>Reported all customer applications patched at 07:48 UTC on 22 October, <strong>approximately 18 hours in<\/strong>. Some services were temporarily disabled as a precaution.<\/td>\n<\/tr>\n<tr>\n<td><strong>Kinsta<\/strong><\/td>\n<td>Reported full coverage at 08:26 UTC on 22 October, <strong>approximately 18.5 hours in<\/strong>. Cloudflare firewall rules provided protection during the rollout.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>I\u2019m proud of how quickly our team responded. But I wouldn\u2019t use a patch-completion table alone to claim that another provider\u2019s customers were unprotected for every hour shown.<\/p>\n<p>The more useful questions are: what protection was in place, which environments did it cover, and how quickly was the permanent fix completed?<\/p>\n<p>Those are questions worth asking your hosting provider.<\/p>\n<h2>Security features matter. So does the team operating them.<\/h2>\n<p>Firewalls, malware detection, access controls and backups all have a role to play.<\/p>\n<p>But a feature list can only tell you so much.<\/p>\n<p>Prior to frontier intelligent models, it was all about security features. Now, it&#8217;s not only about security features but how agile and efficient your infrastructure is to rollout a patch or update. Thankfully, this is where Staq&#8217;s infrastructure upgrade in March 2026 saved the day and made it really efficient and easy for us to deploy.<\/p>\n<h2>Looking for a hosting partner?<\/h2>\n<p>Unfortunately, events like php2shell will happen again. But what this has taught us that a list of security features and taking over 12 hours to respond to such a global event isn&#8217;t good enough. If you&#8217;re looking for a hosting partner that&#8217;s agile, then <a href=\"https:\/\/www.wpstaq.com\/book-demo\/\">please contact us and let&#8217;s have a call<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p>Cheers,<\/p>\n<p>Emmanuel<br \/>\nCEO<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What is now called Black October, the recent php2shell vulnerability caught everyone&#8217;s pants down. The PHP2Shell incident had developers, hosting companies and digital agencies checking their infrastructure while answering the question every client understandably wanted answered: \u201cAre we protected?\u201d Then came the familiar commentary. WordPress isn\u2019t secure. Move to Shopify. Use Webflow. Build a static&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[13],"tags":[],"class_list":["post-89820","post","type-post","status-publish","format-standard","hentry","category-wordpress-security"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Here&#039;s what the recent PHP2Shell has taught us - Managed Hosting Platform for WordPress<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Here&#039;s what the recent PHP2Shell has taught us - Managed Hosting Platform for WordPress\" \/>\n<meta property=\"og:description\" content=\"What is now called Black October, the recent php2shell vulnerability caught everyone&#8217;s pants down. The PHP2Shell incident had developers, hosting companies and digital agencies checking their infrastructure while answering the question every client understandably wanted answered: \u201cAre we protected?\u201d Then came the familiar commentary. WordPress isn\u2019t secure. Move to Shopify. Use Webflow. Build a static&hellip;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/\" \/>\n<meta property=\"og:site_name\" content=\"Managed Hosting Platform for WordPress\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/staqhosting\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-02T23:41:47+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-03T03:36:08+00:00\" \/>\n<meta name=\"author\" content=\"digitalengine\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"digitalengine\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/\"},\"author\":{\"name\":\"digitalengine\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#\\\/schema\\\/person\\\/ffab9ebf1536c5d06baf2790aac09819\"},\"headline\":\"Here&#8217;s what the recent PHP2Shell has taught us\",\"datePublished\":\"2026-11-02T23:41:47+00:00\",\"dateModified\":\"2026-11-03T03:36:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/\"},\"wordCount\":1573,\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#organization\"},\"articleSection\":[\"WordPress Security\"],\"inLanguage\":\"en-sg\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/\",\"url\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/\",\"name\":\"Here's what the recent PHP2Shell has taught us - Managed Hosting Platform for WordPress\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#website\"},\"datePublished\":\"2026-11-02T23:41:47+00:00\",\"dateModified\":\"2026-11-03T03:36:08+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/#breadcrumb\"},\"inLanguage\":\"en-sg\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/post-php2shell-black-october\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.wpstaq.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Here&#8217;s what the recent PHP2Shell has taught us\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#website\",\"url\":\"https:\\\/\\\/www.wpstaq.com\\\/\",\"name\":\"Managed Hosting Platform for WordPress\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.wpstaq.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-sg\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#organization\",\"name\":\"Staq\",\"alternateName\":\"WPStaq\",\"url\":\"https:\\\/\\\/www.wpstaq.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-sg\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.wpstaq.com\\\/wp-content\\\/uploads\\\/2023\\\/05\\\/cropped-LogoNoText.png\",\"contentUrl\":\"https:\\\/\\\/www.wpstaq.com\\\/wp-content\\\/uploads\\\/2023\\\/05\\\/cropped-LogoNoText.png\",\"width\":512,\"height\":512,\"caption\":\"Staq\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/staqhosting\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/wpstaq\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.wpstaq.com\\\/#\\\/schema\\\/person\\\/ffab9ebf1536c5d06baf2790aac09819\",\"name\":\"digitalengine\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-sg\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/534c9cf73b83b0baf8c825182339fc1d53bac0bdd40dda66dc86bcd2ebeb4195?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/534c9cf73b83b0baf8c825182339fc1d53bac0bdd40dda66dc86bcd2ebeb4195?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/534c9cf73b83b0baf8c825182339fc1d53bac0bdd40dda66dc86bcd2ebeb4195?s=96&d=mm&r=g\",\"caption\":\"digitalengine\"},\"url\":\"https:\\\/\\\/www.wpstaq.com\\\/sg\\\/author\\\/digitalengine\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Here's what the recent PHP2Shell has taught us - Managed Hosting Platform for WordPress","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/","og_locale":"en_US","og_type":"article","og_title":"Here's what the recent PHP2Shell has taught us - Managed Hosting Platform for WordPress","og_description":"What is now called Black October, the recent php2shell vulnerability caught everyone&#8217;s pants down. The PHP2Shell incident had developers, hosting companies and digital agencies checking their infrastructure while answering the question every client understandably wanted answered: \u201cAre we protected?\u201d Then came the familiar commentary. WordPress isn\u2019t secure. Move to Shopify. Use Webflow. Build a static&hellip;","og_url":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/","og_site_name":"Managed Hosting Platform for WordPress","article_publisher":"https:\/\/www.facebook.com\/staqhosting\/","article_published_time":"2026-11-02T23:41:47+00:00","article_modified_time":"2026-11-03T03:36:08+00:00","author":"digitalengine","twitter_card":"summary_large_image","twitter_misc":{"Written by":"digitalengine","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/#article","isPartOf":{"@id":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/"},"author":{"name":"digitalengine","@id":"https:\/\/www.wpstaq.com\/#\/schema\/person\/ffab9ebf1536c5d06baf2790aac09819"},"headline":"Here&#8217;s what the recent PHP2Shell has taught us","datePublished":"2026-11-02T23:41:47+00:00","dateModified":"2026-11-03T03:36:08+00:00","mainEntityOfPage":{"@id":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/"},"wordCount":1573,"publisher":{"@id":"https:\/\/www.wpstaq.com\/#organization"},"articleSection":["WordPress Security"],"inLanguage":"en-sg"},{"@type":"WebPage","@id":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/","url":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/","name":"Here's what the recent PHP2Shell has taught us - Managed Hosting Platform for WordPress","isPartOf":{"@id":"https:\/\/www.wpstaq.com\/#website"},"datePublished":"2026-11-02T23:41:47+00:00","dateModified":"2026-11-03T03:36:08+00:00","breadcrumb":{"@id":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/#breadcrumb"},"inLanguage":"en-sg","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.wpstaq.com\/post-php2shell-black-october\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.wpstaq.com\/post-php2shell-black-october\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.wpstaq.com\/"},{"@type":"ListItem","position":2,"name":"Here&#8217;s what the recent PHP2Shell has taught us"}]},{"@type":"WebSite","@id":"https:\/\/www.wpstaq.com\/#website","url":"https:\/\/www.wpstaq.com\/","name":"Managed Hosting Platform for WordPress","description":"","publisher":{"@id":"https:\/\/www.wpstaq.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.wpstaq.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-sg"},{"@type":"Organization","@id":"https:\/\/www.wpstaq.com\/#organization","name":"Staq","alternateName":"WPStaq","url":"https:\/\/www.wpstaq.com\/","logo":{"@type":"ImageObject","inLanguage":"en-sg","@id":"https:\/\/www.wpstaq.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.wpstaq.com\/wp-content\/uploads\/2023\/05\/cropped-LogoNoText.png","contentUrl":"https:\/\/www.wpstaq.com\/wp-content\/uploads\/2023\/05\/cropped-LogoNoText.png","width":512,"height":512,"caption":"Staq"},"image":{"@id":"https:\/\/www.wpstaq.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/staqhosting\/","https:\/\/www.linkedin.com\/company\/wpstaq"]},{"@type":"Person","@id":"https:\/\/www.wpstaq.com\/#\/schema\/person\/ffab9ebf1536c5d06baf2790aac09819","name":"digitalengine","image":{"@type":"ImageObject","inLanguage":"en-sg","@id":"https:\/\/secure.gravatar.com\/avatar\/534c9cf73b83b0baf8c825182339fc1d53bac0bdd40dda66dc86bcd2ebeb4195?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/534c9cf73b83b0baf8c825182339fc1d53bac0bdd40dda66dc86bcd2ebeb4195?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/534c9cf73b83b0baf8c825182339fc1d53bac0bdd40dda66dc86bcd2ebeb4195?s=96&d=mm&r=g","caption":"digitalengine"},"url":"https:\/\/www.wpstaq.com\/sg\/author\/digitalengine\/"}]}},"_links":{"self":[{"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/posts\/89820","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/comments?post=89820"}],"version-history":[{"count":3,"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/posts\/89820\/revisions"}],"predecessor-version":[{"id":89825,"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/posts\/89820\/revisions\/89825"}],"wp:attachment":[{"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/media?parent=89820"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/categories?post=89820"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wpstaq.com\/sg\/wp-json\/wp\/v2\/tags?post=89820"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}